[Gluster-devel] Why is sys_lgetxattr() done under LOCK() in posix_skip_non_linkto_unlink() ?

Yaniv Kaul ykaul at redhat.com
Fri Oct 18 16:24:07 UTC 2019


Can anyone see why we are doing a disk metadata IO under lock here?

        LOCK(&loc->inode->lock);

        xattr_size = sys_lgetxattr(real_path, linkto_xattr, NULL, 0);

        if (xattr_size <= 0)
            skip_unlink = _gf_true;

        UNLOCK(&loc->inode->lock);


TIA,
Y.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20191018/ac45e4ff/attachment.html>


More information about the Gluster-devel mailing list