From: Christian Brauner <brauner@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Mateusz Guzik <mjguzik@gmail.com>,
Josef Bacik <josef@toxicpanda.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fs: try an opportunistic lookup for O_CREAT opens too
Date: Wed, 7 Aug 2024 16:26:46 +0200 [thread overview]
Message-ID: <20240807-erledigen-antworten-6219caebedc0@brauner> (raw)
In-Reply-To: <20240806-openfast-v2-1-42da45981811@kernel.org>
> +static struct dentry *lookup_fast_for_open(struct nameidata *nd, int open_flag)
> +{
> + struct dentry *dentry;
> +
> + if (open_flag & O_CREAT) {
> + /* Don't bother on an O_EXCL create */
> + if (open_flag & O_EXCL)
> + return NULL;
> +
> + /*
> + * FIXME: If auditing is enabled, then we'll have to unlazy to
> + * use the dentry. For now, don't do this, since it shifts
> + * contention from parent's i_rwsem to its d_lockref spinlock.
> + * Reconsider this once dentry refcounting handles heavy
> + * contention better.
> + */
> + if ((nd->flags & LOOKUP_RCU) && !audit_dummy_context())
> + return NULL;
Hm, the audit_inode() on the parent is done independent of whether the
file was actually created or not. But the audit_inode() on the file
itself is only done when it was actually created. Imho, there's no need
to do audit_inode() on the parent when we immediately find that file
already existed. If we accept that then this makes the change a lot
simpler.
The inconsistency would partially remain though. When the file doesn't
exist audit_inode() on the parent is called but by the time we've
grabbed the inode lock someone else might already have created the file
and then again we wouldn't audit_inode() on the file but we would have
on the parent.
I think that's fine. But if that's bothersome the more aggressive thing
to do would be to pull that audit_inode() on the parent further down
after we created the file. Imho, that should be fine?...
See https://gitlab.com/brauner/linux/-/commits/vfs.misc.jeff/?ref_type=heads
for a completely untested draft of what I mean.
next prev parent reply other threads:[~2024-08-07 14:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 14:32 Jeff Layton
2024-08-06 15:25 ` Mateusz Guzik
2024-08-06 16:17 ` Jeff Layton
2024-08-06 16:42 ` Mateusz Guzik
2024-08-06 19:11 ` Andi Kleen
2024-08-06 19:22 ` Mateusz Guzik
2024-08-06 20:42 ` Jeff Layton
2024-08-06 19:26 ` Jeff Layton
2024-08-06 20:03 ` Mateusz Guzik
2024-08-06 20:47 ` Andi Kleen
2024-08-15 15:07 ` Mateusz Guzik
2024-08-06 19:51 ` Jeff Layton
2024-08-14 2:18 ` Al Viro
2024-08-14 2:40 ` Al Viro
2024-08-14 11:48 ` Jeff Layton
2024-08-14 12:40 ` Christian Brauner
2024-08-14 15:44 ` Al Viro
2024-08-16 8:34 ` Christian Brauner
2024-08-14 15:42 ` Al Viro
2024-08-14 16:46 ` Jeff Layton
2024-08-07 14:26 ` Christian Brauner [this message]
2024-08-07 14:36 ` Jeff Layton
2024-08-08 10:36 ` Christian Brauner
2024-08-08 10:54 ` Jeff Layton
2024-08-08 11:18 ` Christian Brauner
2024-08-08 17:11 ` Jan Kara
2024-08-08 21:12 ` Paul Moore
2024-08-08 23:43 ` Jeff Layton
2024-08-09 0:28 ` Paul Moore
2024-08-09 0:33 ` Jeff Layton
2024-08-09 1:22 ` Paul Moore
2024-08-09 14:21 ` Jeff Layton
2024-08-11 21:52 ` Paul Moore
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=20240807-erledigen-antworten-6219caebedc0@brauner \
--to=brauner@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.com \
--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
all inboxes | Powered by JetHome®