diff options
| author | Christian Brauner <brauner@kernel.org> | 2025-11-11 10:38:44 +0100 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2025-11-12 12:19:08 +0100 |
| commit | 04f0955b603cb49eeb752fc8cceca9e9b2f99e14 (patch) | |
| tree | bb2f97126c4e96f55c69c9c6b320e3dac8262429 /fs/open.c | |
| parent | 854e8df2ce6b02c8be40d6f26bd8aa700b375bb2 (diff) | |
| parent | a0a28c4e41251a85b4b6db987a72ffbc8613e497 (diff) | |
| download | tip-04f0955b603cb49eeb752fc8cceca9e9b2f99e14.tar.gz | |
Merge patch series "cheaper MAY_EXEC handling for path lookup"
Mateusz Guzik <mjguzik@gmail.com> says:
In short, MAY_WRITE checks are elided.
This obsoletes the idea of pre-computing if perm checks are necessary as
that turned out to be too hairy. The new code has 2 more branches per
path component compared to that idea, but the perf difference for
typical paths (< 6 components) was basically within noise. To be
revisited if someone(tm) removes other slowdowns.
Instead of the pre-computing thing I added IOP_FASTPERM_MAY_EXEC so that
filesystems like btrfs can still avoid the hard work.
* patches from https://patch.msgid.link/20251107142149.989998-1-mjguzik@gmail.com:
fs: retire now stale MAY_WRITE predicts in inode_permission()
btrfs: utilize IOP_FASTPERM_MAY_EXEC
fs: speed up path lookup with cheaper handling of MAY_EXEC
Link: https://patch.msgid.link/20251107142149.989998-1-mjguzik@gmail.com
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'fs/open.c')
0 files changed, 0 insertions, 0 deletions