From: Jeff Layton <jlayton@kernel.org>
To: Xiubo Li <xiubli@redhat.com>, chuck.lever@oracle.com
Cc: linux-fsdevel@vger.kernel.org, ceph-devel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [RFC PATCH] filelock: new helper: vfs_file_has_locks
Date: Wed, 16 Nov 2022 06:25:49 -0500 [thread overview]
Message-ID: <76c783969445db694a18a35b51fc886c4efe5fb6.camel@kernel.org> (raw)
In-Reply-To: <4fac935b-8e33-2202-48c2-80bdfddc074e@redhat.com>
On Wed, 2022-11-16 at 19:16 +0800, Xiubo Li wrote:
> On 16/11/2022 18:55, Jeff Layton wrote:
> > On Wed, 2022-11-16 at 14:49 +0800, Xiubo Li wrote:
> > > On 15/11/2022 22:40, Jeff Layton wrote:
> > >
> ...
> > > > + spin_lock(&ctx->flc_lock);
> > > > + ret = !list_empty(&ctx->flc_posix) || !list_empty(&ctx->flc_flock);
> > > > + spin_unlock(&ctx->flc_lock);
> > > BTW, is the spin_lock/spin_unlock here really needed ?
> > >
> > We could probably achieve the same effect with barriers, but I doubt
> > it's worth it. The flc_lock only protects the lists in the
> > file_lock_context, so it should almost always be uncontended.
> >
> I just see some other places where are also checking this don't use the
> spin lock.
>
>
True.
There are a number of places that don't and that use list_empty_careful.
Some of those We could convert to that here, but again, I'm not sure
it's worth it. Let's stick with using the spinlocks here, since this
isn't a performance-critical codepath anyway.
>
> > > > + return ret;
> > > > +}
> > > > +EXPORT_SYMBOL_GPL(vfs_inode_has_locks);
> > > > +
> > > > #ifdef CONFIG_PROC_FS
> > > > #include <linux/proc_fs.h>
> > > > #include <linux/seq_file.h>
> > > > diff --git a/include/linux/fs.h b/include/linux/fs.h
> > > > index e654435f1651..d6cb42b7e91c 100644
> > > > --- a/include/linux/fs.h
> > > > +++ b/include/linux/fs.h
> > > > @@ -1170,6 +1170,7 @@ extern int locks_delete_block(struct file_lock *);
> > > > extern int vfs_test_lock(struct file *, struct file_lock *);
> > > > extern int vfs_lock_file(struct file *, unsigned int, struct file_lock *, struct file_lock *);
> > > > extern int vfs_cancel_lock(struct file *filp, struct file_lock *fl);
> > > > +bool vfs_inode_has_locks(struct inode *inode);
> > > > extern int locks_lock_inode_wait(struct inode *inode, struct file_lock *fl);
> > > > extern int __break_lease(struct inode *inode, unsigned int flags, unsigned int type);
> > > > extern void lease_get_mtime(struct inode *, struct timespec64 *time);
> > > All the others LGTM.
> > >
> > > Thanks.
> > >
> > > - Xiubo
> > >
> > >
> > Thanks. I'll re-post it "officially" in a bit and will queue it up for
> > v6.2.
>
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2022-11-16 11:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 14:07 [RFC PATCH] filelock: new helper: vfs_file_has_locks Jeff Layton
2022-11-14 14:19 ` Chuck Lever III
2022-11-14 19:46 ` Jeff Layton
2022-11-15 5:43 ` Xiubo Li
2022-11-15 14:40 ` Jeff Layton
2022-11-16 6:16 ` Christoph Hellwig
2022-11-16 6:49 ` Xiubo Li
2022-11-16 10:55 ` Jeff Layton
2022-11-16 11:16 ` Xiubo Li
2022-11-16 11:25 ` Jeff Layton [this message]
2022-11-16 13:24 ` Xiubo Li
2022-11-15 8:54 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76c783969445db694a18a35b51fc886c4efe5fb6.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=chuck.lever@oracle.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=xiubli@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).