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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 18 Oct 2020 16:04:35 +0100 From: Matthew Wilcox <willy@...radead.org> To: "Theodore Y. Ts'o" <tytso@....edu> Cc: linux-fsdevel@...r.kernel.org, linux-mm@...ck.org, Andreas Dilger <adilger.kernel@...ger.ca>, linux-ext4@...r.kernel.org Subject: Re: [PATCH v3 12/18] ext4: Return error from ext4_readpage On Sun, Oct 18, 2020 at 10:25:57AM -0400, Theodore Y. Ts'o wrote: > On Fri, Oct 16, 2020 at 05:04:37PM +0100, Matthew Wilcox (Oracle) wrote: > > The error returned from ext4_map_blocks() was being discarded, leading > > to the generic -EIO being returned to userspace. Now ext4 can return > > more precise errors. > > > > Signed-off-by: Matthew Wilcox (Oracle) <willy@...radead.org> > > This change is independent of the synchronous readpage changes, > correct? Or am I missing something? It's a step along the way. If you want to queue it up independently of the other changes, I see no problem with that. The requirement to make a synchronous ->readpage killable is making the conversion quite thorny and I'm not sure I'm going to get it done this merge window.
Powered by blists - more mailing lists