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: Mon, 14 Nov 2022 18:20:37 +0000 From: Eric Biggers <ebiggers@...nel.org> To: Alexander Potapenko <glider@...gle.com> Cc: linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, tytso@....edu, adilger.kernel@...ger.ca, jaegeuk@...nel.org, chao@...nel.org, linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org, syzbot+9767be679ef5016b6082@...kaller.appspotmail.com Subject: Re: [PATCH] fs: ext4: initialize fsdata in pagecache_write() On Mon, Nov 14, 2022 at 09:29:35AM +0100, Alexander Potapenko wrote: > [PATCH] fs: ext4: initialize fsdata in pagecache_write() > > When aops->write_begin() does not initialize fsdata, KMSAN reports > an error passing the latter to aops->write_end(). > > Fix this by unconditionally initializing fsdata. > > Also speculatively fix similar issues in affs, f2fs, hfs, hfsplus, > as suggested by Eric Biggers. You might have better luck with separate patches for each filesystem, as it might be hard to get someone to apply this patch otherwise. If you do go with a single patch, then the subject prefix should be "fs:", not "fs: ext4:". - Eric
Powered by blists - more mailing lists