From: Amir Goldstein <amir73il@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
overlayfs <linux-unionfs@vger.kernel.org>,
linux-cachefs@redhat.com, Christoph Hellwig <hch@infradead.org>,
Jeff Layton <jlayton@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/5] vfs: Add tracepoints for inode_excl_inuse_trylock/unlock
Date: Mon, 31 Jan 2022 17:32:08 +0200 [thread overview]
Message-ID: <CAOQ4uxit42u7BSM_UAOc9gFsDb5b9JeEh1m_gCKMO7pxrtsAiA@mail.gmail.com> (raw)
In-Reply-To: <164364202369.1476539.452557132083658522.stgit@warthog.procyon.org.uk>
On Mon, Jan 31, 2022 at 5:13 PM David Howells <dhowells@redhat.com> wrote:
>
> Add tracepoints for inode_excl_inuse_trylock/unlock() to record successful
> and lock, failed lock, successful unlock and unlock when it wasn't locked.
>
> Signed-off-by: David Howells <dhowells@redhat.com>
> cc: Amir Goldstein <amir73il@gmail.com>
> cc: Miklos Szeredi <miklos@szeredi.hu>
> cc: linux-unionfs@vger.kernel.org
> cc: linux-cachefs@redhat.com
> ---
>
> fs/inode.c | 21 +++++++++++++++++----
> fs/overlayfs/super.c | 10 ++++++----
> include/linux/fs.h | 9 +++++++--
> 3 files changed, 30 insertions(+), 10 deletions(-)
>
> diff --git a/fs/inode.c b/fs/inode.c
> index 954719f66113..61b93a89853f 100644
> --- a/fs/inode.c
> +++ b/fs/inode.c
> @@ -22,6 +22,8 @@
> #include <linux/iversion.h>
> #include <trace/events/writeback.h>
> #include "internal.h"
> +#define CREATE_TRACE_POINTS
> +#include <trace/events/vfs.h>
>
> /*
> * Inode locking rules:
> @@ -2409,11 +2411,14 @@ EXPORT_SYMBOL(current_time);
> /**
> * inode_excl_inuse_trylock - Try to exclusively lock an inode for kernel access
> * @dentry: Reference to the inode to be locked
> + * @o: Private reference for the kernel service
> + * @who: Which kernel service is trying to gain the lock
> *
> * Try to gain exclusive access to an inode for a kernel service, returning
> * true if successful.
> */
> -bool inode_excl_inuse_trylock(struct dentry *dentry)
> +bool inode_excl_inuse_trylock(struct dentry *dentry, unsigned int o,
> + enum inode_excl_inuse_by who)
> {
> struct inode *inode = d_inode(dentry);
> bool locked = false;
> @@ -2421,7 +2426,10 @@ bool inode_excl_inuse_trylock(struct dentry *dentry)
> spin_lock(&inode->i_lock);
> if (!(inode->i_state & I_EXCL_INUSE)) {
> inode->i_state |= I_EXCL_INUSE;
> + trace_inode_excl_inuse_lock(inode, o, who);
> locked = true;
> + } else {
> + trace_inode_excl_inuse_lock_failed(inode, o, who);
> }
> spin_unlock(&inode->i_lock);
>
> @@ -2432,18 +2440,23 @@ EXPORT_SYMBOL(inode_excl_inuse_trylock);
> /**
> * inode_excl_inuse_unlock - Unlock exclusive kernel access to an inode
> * @dentry: Reference to the inode to be unlocked
> + * @o: Private reference for the kernel service
> *
> * Drop exclusive access to an inode for a kernel service. A warning is given
> * if the inode was not marked for exclusive access.
> */
> -void inode_excl_inuse_unlock(struct dentry *dentry)
> +void inode_excl_inuse_unlock(struct dentry *dentry, unsigned int o)
> {
> if (dentry) {
> struct inode *inode = d_inode(dentry);
>
> spin_lock(&inode->i_lock);
> - WARN_ON(!(inode->i_state & I_EXCL_INUSE));
> - inode->i_state &= ~I_EXCL_INUSE;
> + if (WARN_ON(!(inode->i_state & I_EXCL_INUSE))) {
> + trace_inode_excl_inuse_unlock_bad(inode, o);
> + } else {
> + inode->i_state &= ~I_EXCL_INUSE;
> + trace_inode_excl_inuse_unlock(inode, o);
> + }
> spin_unlock(&inode->i_lock);
> }
> }
> diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
> index 5c3361a2dc7c..6434ae11496d 100644
> --- a/fs/overlayfs/super.c
> +++ b/fs/overlayfs/super.c
> @@ -224,10 +224,10 @@ static void ovl_free_fs(struct ovl_fs *ofs)
> dput(ofs->indexdir);
> dput(ofs->workdir);
> if (ofs->workdir_locked)
> - inode_excl_inuse_unlock(ofs->workbasedir);
> + inode_excl_inuse_unlock(ofs->workbasedir, 0);
> dput(ofs->workbasedir);
> if (ofs->upperdir_locked)
> - inode_excl_inuse_unlock(ovl_upper_mnt(ofs)->mnt_root);
> + inode_excl_inuse_unlock(ovl_upper_mnt(ofs)->mnt_root, 0);
>
> /* Hack! Reuse ofs->layers as a vfsmount array before freeing it */
> mounts = (struct vfsmount **) ofs->layers;
> @@ -1239,7 +1239,8 @@ static int ovl_get_upper(struct super_block *sb, struct ovl_fs *ofs,
> if (upper_mnt->mnt_sb->s_flags & SB_NOSEC)
> sb->s_flags |= SB_NOSEC;
>
> - if (inode_excl_inuse_trylock(ovl_upper_mnt(ofs)->mnt_root)) {
> + if (inode_excl_inuse_trylock(ovl_upper_mnt(ofs)->mnt_root, 0,
> + inode_excl_inuse_by_overlayfs)) {
> ofs->upperdir_locked = true;
> } else {
> err = ovl_report_in_use(ofs, "upperdir");
> @@ -1499,7 +1500,8 @@ static int ovl_get_workdir(struct super_block *sb, struct ovl_fs *ofs,
>
> ofs->workbasedir = dget(workpath.dentry);
>
> - if (inode_excl_inuse_trylock(ofs->workbasedir)) {
> + if (inode_excl_inuse_trylock(ofs->workbasedir, 0,
> + inode_excl_inuse_by_overlayfs)) {
More incentive to keep the ovl_* wrappers.
Thanks,
Amir.
next prev parent reply other threads:[~2022-01-31 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 15:12 [RFC][PATCH 0/5] vfs, overlayfs, cachefiles: Combine I_OVL_INUSE and S_KERNEL_FILE and split out no-remove David Howells
2022-01-31 15:12 ` [PATCH 1/5] vfs, overlayfs, cachefiles: Turn I_OVL_INUSE into something generic David Howells
2022-01-31 15:29 ` Amir Goldstein
2022-01-31 15:32 ` David Howells
2022-01-31 16:20 ` Amir Goldstein
2022-01-31 15:13 ` [PATCH 2/5] vfs: Add tracepoints for inode_excl_inuse_trylock/unlock David Howells
2022-01-31 15:32 ` Amir Goldstein [this message]
2022-01-31 15:13 ` [PATCH 3/5] cachefiles: Split removal-prevention from S_KERNEL_FILE and extend effects David Howells
2022-01-31 15:14 ` [PATCH 4/5] cachefiles: Use I_EXCL_INUSE instead of S_KERNEL_FILE David Howells
2022-01-31 15:14 ` [PATCH 5/5] cachefiles: Remove the now-unused mark-inode-in-use tracepoints David Howells
2022-01-31 16:28 ` [RFC][PATCH 0/5] vfs, overlayfs, cachefiles: Combine I_OVL_INUSE and S_KERNEL_FILE and split out no-remove Amir Goldstein
2022-02-01 10:44 ` [PATCH 2/5] vfs: Add tracepoints for inode_excl_inuse_trylock/unlock David Howells
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=CAOQ4uxit42u7BSM_UAOc9gFsDb5b9JeEh1m_gCKMO7pxrtsAiA@mail.gmail.com \
--to=amir73il@gmail.com \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=jlayton@kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).