aboutsummaryrefslogtreecommitdiff
path: root/fs/crypto/hooks.c
diff options
context:
space:
mode:
authorGravatar Eric Biggers <ebiggers@google.com> 2022-08-15 16:50:51 -0700
committerGravatar Eric Biggers <ebiggers@google.com> 2022-09-06 15:15:56 -0700
commit14db0b3c7b837f4edeb7c1794290c2f345c7f627 (patch)
tree910d1d1587b9e30030ba477777d42cacf1fac462 /fs/crypto/hooks.c
parentfscrypt: remove fscrypt_set_test_dummy_encryption() (diff)
downloadlinux-14db0b3c7b837f4edeb7c1794290c2f345c7f627.tar.gz
linux-14db0b3c7b837f4edeb7c1794290c2f345c7f627.tar.bz2
linux-14db0b3c7b837f4edeb7c1794290c2f345c7f627.zip
fscrypt: stop using PG_error to track error status
As a step towards freeing the PG_error flag for other uses, change ext4 and f2fs to stop using PG_error to track decryption errors. Instead, if a decryption error occurs, just mark the whole bio as failed. The coarser granularity isn't really a problem since it isn't any worse than what the block layer provides, and errors from a multi-page readahead aren't reported to applications unless a single-page read fails too. Signed-off-by: Eric Biggers <ebiggers@google.com> Reviewed-by: Chao Yu <chao@kernel.org> # for f2fs part Link: https://lore.kernel.org/r/20220815235052.86545-2-ebiggers@kernel.org
Diffstat (limited to 'fs/crypto/hooks.c')
0 files changed, 0 insertions, 0 deletions