linux-ext4 - Re: [PATCH AUTOSEL 6.1 08/14] ext4: enable dioread

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZabrcCOi/hIsKk5I@duo.ucw.cz>
Date: Tue, 16 Jan 2024 21:47:44 +0100
From: Pavel Machek <pavel@...x.de>
To: Sasha Levin <sashal@...nel.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	Ojaswin Mujoo <ojaswin@...ux.ibm.com>,
	Ritesh Harjani <ritesh.list@...il.com>,
	Theodore Ts'o <tytso@....edu>, adilger.kernel@...ger.ca,
	linux-ext4@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 6.1 08/14] ext4: enable dioread_nolock as default
 for bs < ps case

Hi!
> 
> [ Upstream commit e89fdcc425b6feea4dfb33877e9256757905d763 ]
> 
> dioread_nolock was originally disabled as a default option for bs < ps
> scenarios due to a data corruption issue. Since then, we've had some
> fixes in this area which address such issues. Enable dioread_nolock by
> default and remove the experimental warning message for bs < ps path.
> 
> dioread for bs < ps has been tested on a 64k pagesize machine using:
> 
> kvm-xfstest -C 3 -g auto
> 
> with the following configs:
> 
> 64k adv bigalloc_4k bigalloc_64k data_journal encrypt
> dioread_nolock dioread_nolock_4k ext3 ext3conv nojournal
> 
> And no new regressions were seen compared to baseline kernel.

But no fixes, either, so not suitable for stable.

BR,
								Pavel

-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)