From: Jeff Layton <firstname.lastname@example.org>
To: Dave Chinner <email@example.com>
Cc: firstname.lastname@example.org, email@example.com,
Al Viro <firstname.lastname@example.org>, Christoph Hellwig <email@example.com>
Subject: Re: [PATCH v2] fs: change test in inode_insert5 for adding to the sb list
Date: Thu, 12 May 2022 11:51:09 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Fri, 2022-05-13 at 00:21 +1000, Dave Chinner wrote:
> On Wed, May 11, 2022 at 12:53:39PM -0400, Jeff Layton wrote:
> > The inode_insert5 currently looks at I_CREATING to decide whether to
> > insert the inode into the sb list. This test is a bit ambiguous though
> > as I_CREATING state is not directly related to that list.
> > This test is also problematic for some upcoming ceph changes to add
> > fscrypt support. We need to be able to allocate an inode using new_inode
> > and insert it into the hash later if we end up using it, and doing that
> > now means that we double add it and corrupt the list.
> > What we really want to know in this test is whether the inode is already
> > in its superblock list, and then add it if it isn't. Have it test for
> > list_empty instead and ensure that we always initialize the list by
> > doing it in inode_init_once. It's only ever removed from the list with
> > list_del_init, so that should be sufficient.
> > There doesn't seem to be any need to hold the inode_hash_lock for this
> > operation either, so drop that before adding to to the list.
> > Suggested-by: Al Viro <email@example.com>
> > Cc: Dave Chinner <firstname.lastname@example.org>
> > Signed-off-by: Jeff Layton <email@example.com>
> > Signed-off-by: Ilya Dryomov <firstname.lastname@example.org>
> > ---
> > fs/inode.c | 13 +++++++++----
> > 1 file changed, 9 insertions(+), 4 deletions(-)
> > A small revision to the patch that I sent as part of the ceph+fscrypt
> > series. I didn't see any need to hold the inode_hash_lock when adding
> > the inode to the sb list, so do that outside the lock. I also revised
> > the comment to be more clear.
> I'm not sure that's valid. The moment the hash lock is dropped,
> other lookups can find this inode in the cache. Hence there's no
> guarantee that someone else isn't already accessing the inode
> once the hash lock is dropped. Hence it's not clear to me that this
> is a safe modification to make.
> Given that we already do the list add under the hash lock, I don't
> see any real gain to removing it from that context and it isn't
> necessary to address the problem.
> If you are concerned about reducing inode_has_lock contention, then
> the answer to that is to convert the global lock to bit list locks
> as the dentry cache uses. I wrote a patch a while back to do this:
> Hence at this stage, I prefer the original version that doesn't
> change locking because there's much less risk associated with it.
I didn't see anything that cares about the i_sb_list while
simultaneously holding the inode_hash_lock. It gets removed from the
list in evict, but we hold a reference to it at this point, so
nothingThe thing also has I_NEW set on it so there had better not be
That said, iget_locked also holds it while adding it to the list and
you're correct that it's not required to fix the problem. I'll plan to
revert it to the v1 version. We can always experiment with moving it
outside the lock later if we think that's useful.
Christoph, are you OK with the original version of that patch as well? I
can resend it again if you missed it the first time.
Jeff Layton <email@example.com>
next prev parent reply other threads:[~2022-05-12 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 16:53 [PATCH v2] fs: change test in inode_insert5 for adding to the sb list Jeff Layton
2022-05-12 6:21 ` Christoph Hellwig
2022-05-12 14:21 ` Dave Chinner
2022-05-12 15:51 ` Jeff Layton [this message]
2022-06-27 11:15 ` Jeff Layton
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.