[Bugs] [Bug 1467614] Gluster read/write performance improvements on NVMe backend

[bugzilla at redhat.com]

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



--- Comment #17 from Raghavendra G <rgowdapp at redhat.com> ---
> * Replacing inode_table->lock with inode->lock will lead to correctness issues and possible corruption in inode_unref() since inode_unref() does not merely decrement ref count but also operates on inode_table and the lists within it. So it is necessary to acquire inode_table->lock when performing inode_unref(). The old (existing) code is correct.

We can acquire lock only when refcount becomes zero (that's when we modify
various lists). I guess there are lots of inode_unrefs the execution of which
don't result in refcount becoming 0.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=sDpDe95pl4&a=cc_unsubscribe