From: Mateusz Guzik <mjguzik@gmail.com>
To: brauner@kernel.org
Cc: viro@zeniv.linux.org.uk, jack@suse.cz,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, tytso@mit.edu,
torvalds@linux-foundation.org, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, Mateusz Guzik <mjguzik@gmail.com>
Subject: [PATCH v2 4/4] tmpfs: opt-in for IOP_MAY_FAST_EXEC
Date: Thu, 6 Nov 2025 19:01:02 +0100 [thread overview]
Message-ID: <20251106180103.923856-5-mjguzik@gmail.com> (raw)
In-Reply-To: <20251106180103.923856-1-mjguzik@gmail.com>
Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
---
mm/shmem.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/mm/shmem.c b/mm/shmem.c
index c819cecf1ed9..265456bc6bf0 100644
--- a/mm/shmem.c
+++ b/mm/shmem.c
@@ -3106,6 +3106,15 @@ static struct inode *__shmem_get_inode(struct mnt_idmap *idmap,
}
lockdep_annotate_inode_mutex_key(inode);
+
+ if (S_ISDIR(mode)) {
+ WARN_ON_ONCE(inode_state_read_once(inode) & I_NEW);
+ /* satisfy an assert inside */
+ inode_state_set_raw(inode, I_NEW);
+ inode_enable_fast_may_exec(inode);
+ inode_state_clear_raw(inode, I_NEW);
+ }
+
return inode;
}
--
2.48.1
next prev parent reply other threads:[~2025-11-06 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 18:00 [PATCH v2 0/4] permission check avoidance during lookup Mateusz Guzik
2025-11-06 18:00 ` [PATCH v2 1/4] fs: speed up path lookup with cheaper MAY_EXEC checks Mateusz Guzik
2025-11-06 22:45 ` Mateusz Guzik
2025-11-06 18:01 ` [PATCH v2 2/4] ext4: opt-in for IOP_MAY_FAST_EXEC Mateusz Guzik
2025-11-06 18:01 ` [PATCH v2 3/4] btrfs: " Mateusz Guzik
2025-11-06 18:01 ` Mateusz Guzik [this message]
2025-11-06 19:34 ` [PATCH v2 0/4] permission check avoidance during lookup Mateusz Guzik
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=20251106180103.923856-5-mjguzik@gmail.com \
--to=mjguzik@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--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®