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: Fri, 10 Jun 2022 10:00:58 +0200 From: Christoph Hellwig <hch@....de> To: Jan Kara <jack@...e.cz> Cc: Christoph Hellwig <hch@....de>, Matthew Wilcox <willy@...radead.org>, Jan Kara <jack@...e.com>, Dave Kleikamp <shaggy@...nel.org>, linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, jfs-discussion@...ts.sourceforge.net Subject: Re: [PATCH 4/5] fs: don't call ->writepage from __mpage_writepage On Thu, Jun 09, 2022 at 07:31:19PM +0200, Jan Kara wrote: > On Wed 08-06-22 17:04:50, Christoph Hellwig wrote: > > All callers of mpage_writepage use block_write_full_page as their > > ->writepage implementation, so hard code that. > > > > Signed-off-by: Christoph Hellwig <hch@....de> > > Similarly here NTFS (fs/ntfs3/) seems to have some non-trivial stuff besides > block_write_full_page()... Indeed, ntfs3 will need a prep patch to unwind this mess. Thanks for catching this!
Powered by blists - more mailing lists