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@xxxxxxx>
