[Bugs] [Bug 1241487] New: quota/marker: lk_owner is null while acquiring inodelk in rename operation

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1241487

            Bug ID: 1241487
           Summary: quota/marker: lk_owner is null while acquiring inodelk
                    in rename operation
           Product: GlusterFS
           Version: 3.7.2
         Component: quota
          Assignee: bugs at gluster.org
          Reporter: vmallika at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com
        Depends On: 1240598
            Blocks: 1241048



+++ This bug was initially created as a clone of Bug #1240598 +++

Before doing a rename operation marker takes inode lock on the file parent,
here lk_owner is NULL and this can cause accounting problem with multiple
rename on the same directory

--- Additional comment from Anand Avati on 2015-07-07 06:41:14 EDT ---

REVIEW: http://review.gluster.org/11561 (quota/marker: set lk_owner when taking
lock on parent in rename) posted (#1) for review on master by Vijaikumar
Mallikarjuna (vmallika at redhat.com)

--- Additional comment from Anand Avati on 2015-07-07 08:57:01 EDT ---

REVIEW: http://review.gluster.org/11561 (quota/marker: set lk_owner when taking
lock on parent in rename) posted (#2) for review on master by Vijaikumar
Mallikarjuna (vmallika at redhat.com)


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1240598
[Bug 1240598] quota/marker: lk_owner is null while acquiring inodelk in
rename operation
https://bugzilla.redhat.com/show_bug.cgi?id=1241048
[Bug 1241048] quota/marker: lk_owner is null while acquiring inodelk in
rename operation
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.