fscrypt: stop using PG_error to track error status

Browse source

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

...

This commit is contained in:

Eric Biggers 2022-08-15 16:50:51 -07:00

parent 272ac15003

commit 14db0b3c7b

4 changed files with 29 additions and 20 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

16

fs/crypto/bio.c

View file

10

fs/ext4/readpage.c

View file

18

fs/f2fs/data.c

View file

5

include/linux/fscrypt.h

View file