lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <faa8d9e8-f601-ebff-68f7-4e12862391de@kernel.org> Date: Tue, 6 Sep 2022 23:09:17 +0800 From: Chao Yu <chao@...nel.org> To: Eric Biggers <ebiggers@...nel.org>, linux-fscrypt@...r.kernel.org Cc: linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org, Matthew Wilcox <willy@...radead.org>, linux-f2fs-devel@...ts.sourceforge.net Subject: Re: [f2fs-dev] [PATCH v2 1/2] fscrypt: stop using PG_error to track error status On 2022/8/16 7:50, Eric Biggers wrote: > From: Eric Biggers <ebiggers@...gle.com> > > 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@...gle.com> > --- > 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@...nel.org> Thanks,
Powered by blists - more mailing lists