linux-ext4 - Re: significant drop fio IOPS performance on v5.10 #forregzbot

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]

Date:   Thu, 29 Sep 2022 07:36:20 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     Thorsten Leemhuis <regressions@...mhuis.info>
Cc:     "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: significant drop fio IOPS performance on v5.10 #forregzbot

This is a repeat of a discussion regarding changing the default of
dioread_nolock.  Note that you can "revert" this change in defaults by
using the mount options "nodioread_nolock" (or "dioread_lock").  There
were some good reasons why the change in the default was made, though.

#regzbot invalid: caused by a change of defaults that (among others) was
done for security reasons, see Ted's answer in
https://lore.kernel.org/all/Yypx6VQRbl3bFP2v@mit.edu/ for details

					- Ted