diff options
| author | Alberto Garcia <berto@igalia.com> | 2026-09-25 16:19:19 +0200 |
|---|---|---|
| committer | Eric Biggers <ebiggers@kernel.org> | 2026-10-24 12:58:37 -0700 |
| commit | a5e894bc87b76fd980075892ba77e6bdeeb5e4d0 (patch) | |
| tree | f42a58dcfb9fd9a978e3d343f27d269a27a19bd8 /tools/perf/scripts/python/bin/sctop-report | |
| parent | 0e341d1d29db11c29211d2b8870a515c26589d5a (diff) | |
ext4: reject encrypted inodes when block size > page size
Encryption is not supported when a filesystem's block size is larger
than the page size. ext4_check_large_folio() refuses to mount a
filesystem like that if the "encrypt" feature is already enabled, and
ext4_set_context() refuses to create encrypted inodes if the feature
is enabled after mounting.
However, a corrupted or hand-crafted filesystem can still have
encrypted inodes even if the "encrypt" feature is not set, and those
inodes can be unlocked if they're using v1 policies.
Check this in __ext4_iget() and reject them as corrupted.
Fixes: 709f0f1f1bf5 ("ext4: add checks for large folio incompatibilities when BS > PS")
Suggested-by: Eric Biggers <ebiggers@kernel.org>
Cc: stable@vger.kernel.org # v6.19+
Signed-off-by: Alberto Garcia <berto@igalia.com>
Reviewed-by: Baokun Li <libaokun@linux.alibaba.com>
Reviewed-by: Eric Biggers <ebiggers@kernel.org>
Link: https://patch.msgid.link/aeb8efa8beb72721fb4b13cffe6eb22c795ec33f.1790343958.git.berto@igalia.com
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/sctop-report')
0 files changed, 0 insertions, 0 deletions