| 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: <2d7aac9d-8c47-45e1-a058-35e1de80db22@kernel.dk> Date: Thu, 21 Nov 2024 07:48:39 -0700 From: Jens Axboe <axboe@...nel.dk> To: Christoph Hellwig <hch@....de> Cc: Chaitanya Kulkarni <chaitanyak@...dia.com>, Saeed Mirzamohammadi <saeed.mirzamohammadi@...cle.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>, Ramanan Govindarajan <ramanan.govindarajan@...cle.com>, Sagi Grimberg <sagi@...mberg.me>, Paul Webb <paul.x.webb@...cle.com>, Keith Busch <kbusch@...nel.org> Subject: Re: [bug-report] 5-9% FIO randomwrite ext4 perf regression on 6.12.y kernel On 11/20/24 9:57 PM, Christoph Hellwig wrote: > On Wed, Nov 20, 2024 at 06:20:12PM -0700, Jens Axboe wrote: >> There's no way that commit is involved, the test as quoted doesn't even >> touch write zeroes. Hence if there really is a regression here, then >> it's either not easily bisectable, some error was injected while >> bisecting, or the test itself is bimodal. > > ext4 actually has some weird lazy init code using write zeroes. So > if the test actually wasn't a steady state one but only run for a short > time after init, and the mentioned commit dropped the intel hack for > deallocate as write zeroes it might actually make a difference. Ah good point, I forgot about the ext4 lazy init. But any test should surely quiesce that first, not great to have background activity with that. -- Jens Axboe
Powered by blists - more mailing lists