[Bugs] [Bug 1737291] New: features/locks: avoid use after freed of frame for blocked lock

bugzilla at redhat.com bugzilla at redhat.com
Mon Aug 5 03:20:44 UTC 2019


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

            Bug ID: 1737291
           Summary: features/locks: avoid use after freed of frame for
                    blocked lock
           Product: GlusterFS
           Version: mainline
            Status: NEW
         Component: locks
          Assignee: bugs at gluster.org
          Reporter: kinglongmee at gmail.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community



Description of problem:

The fop contains blocked lock may use freed frame info when other unlock fop
has unwind the blocked lock.

Because the blocked lock is added to block list in inode lock(or other lock),
after that, when out of the inode lock, the fop contains the blocked lock
should not use it.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list