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