Re: [f2fs-dev] [PATCH v2 1/2] fscrypt: stop using PG_error to track error status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2022/8/16 7:50, Eric Biggers wrote:
From: Eric Biggers <ebiggers@xxxxxxxxxx>

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@xxxxxxxxxx>
---
  fs/crypto/bio.c         | 16 ++++++++++------
  fs/ext4/readpage.c      |  8 +++++---
  fs/f2fs/data.c          | 18 ++++++++++--------
  include/linux/fscrypt.h |  5 +++--
  4 files changed, 28 insertions(+), 19 deletions(-)

For f2fs part,

Reviewed-by: Chao Yu <chao@xxxxxxxxxx>

Thanks,



[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux