From: Christoph Hellwig <hch@infradead.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: chuck.lever@oracle.com, xiubli@redhat.com,
linux-fsdevel@vger.kernel.org, ceph-devel@vger.kernel.org
Subject: Re: [RFC PATCH] filelock: new helper: vfs_file_has_locks
Date: Tue, 15 Nov 2022 00:54:31 -0800 [thread overview]
Message-ID: <Y3NTx/x2m/kAZyGE@infradead.org> (raw)
In-Reply-To: <20221114140747.134928-1-jlayton@kernel.org>
On Mon, Nov 14, 2022 at 09:07:47AM -0500, Jeff Layton wrote:
> +bool vfs_file_has_locks(struct file *filp)
> +{
> + struct file_lock_context *ctx;
> + struct file_lock *fl;
> + bool ret = false;
> +
> + ctx = smp_load_acquire(&locks_inode(filp)->i_flctx);
> + if (!ctx)
> + return false;
> +
> + spin_lock(&ctx->flc_lock);
> + list_for_each_entry(fl, &ctx->flc_posix, fl_list) {
> + if (fl->fl_file == filp) {
> + ret = true;
> + goto out;
> + }
> + }
> + list_for_each_entry(fl, &ctx->flc_flock, fl_list) {
> + if (fl->fl_file == filp) {
> + ret = true;
> + break;
> + }
> + }
Maybe a little helper for the list lookup would be nice here:
static inline bool __vfs_file_has_locks(struct file *file)
{
struct file_lock *fl;
list_for_each_entry(fl, &ctx->flc_flock, fl_list)
if (fl->fl_file == filp)
return true;
return false;
}
simplifying the check in the caller to:
ret = __vfs_file_has_locks(&ctx->flc_posix) ||
__vfs_file_has_locks(&ctx->flc_flock);
> +EXPORT_SYMBOL(vfs_file_has_locks);
EXPORT_SYMBOL_GPL for any new network-fsy functionality would be nice.
prev parent reply other threads:[~2022-11-15 8:55 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
2022-11-16 13:24 ` Xiubo Li
2022-11-15 8:54 ` Christoph Hellwig [this message]
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=Y3NTx/x2m/kAZyGE@infradead.org \
--to=hch@infradead.org \
--cc=ceph-devel@vger.kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.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).