diff options
| author | Ojaswin Mujoo <[email protected]> | 2023-11-01 21:17:17 +0530 |
|---|---|---|
| committer | Theodore Ts'o <[email protected]> | 2024-01-04 23:28:47 -0500 |
| commit | e89fdcc425b6feea4dfb33877e9256757905d763 (patch) | |
| tree | b355cede78cf573ff582cd13524c72028f2848cf /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | f2fec3e99a32d7c14dbf63c824f8286ebc94b18d (diff) | |
ext4: enable dioread_nolock as default for bs < ps case
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.
Suggested-by: Ritesh Harjani (IBM) <[email protected]>
Signed-off-by: Ojaswin Mujoo <[email protected]>
Reviewed-by: Ritesh Harjani (IBM) <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Theodore Ts'o <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions