linux-ext4 - Re: [PATCH] ext4: Enable dioread_nolock as default for bs

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] [day] [month] [year] [list]

Message-ID: <170476879010.637731.8792821246041124123.b4-ty@mit.edu>
Date: Mon,  8 Jan 2024 21:53:19 -0500
From: "Theodore Ts'o" <tytso@....edu>
To: linux-ext4@...r.kernel.org, Ojaswin Mujoo <ojaswin@...ux.ibm.com>
Cc: "Theodore Ts'o" <tytso@....edu>, Ritesh Harjani <ritesh.list@...il.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ext4: Enable dioread_nolock as default for bs < ps case


On Wed, 01 Nov 2023 21:17:17 +0530, Ojaswin Mujoo wrote:
> 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:
> 
> [...]

Applied, thanks!

[1/1] ext4: Enable dioread_nolock as default for bs < ps case
      commit: e89fdcc425b6feea4dfb33877e9256757905d763

Best regards,
-- 
Theodore Ts'o <tytso@....edu>