fscrypt: stop using PG_error to track error status
authorEric Biggers <ebiggers@google.com>
Mon, 15 Aug 2022 23:50:51 +0000 (16:50 -0700)
committerEric Biggers <ebiggers@google.com>
Tue, 6 Sep 2022 22:15:56 +0000 (15:15 -0700)
commit14db0b3c7b837f4edeb7c1794290c2f345c7f627
tree910d1d1587b9e30030ba477777d42cacf1fac462
parent272ac1500372183ffd54b0c9f43f52afc482e610
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
fs/crypto/bio.c
fs/ext4/readpage.c
fs/f2fs/data.c
include/linux/fscrypt.h