diff options
| author | Ritesh Harjani <riteshh@linux.ibm.com> | 2020-03-28 01:37:44 +0530 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2020-03-28 23:11:04 -0400 |
| commit | 626b035b816b61a7a7b4d2205a6807e2f11a18c1 (patch) | |
| tree | f6fbae6c313068edf8a237d851efc1d0e3aa7305 /fs/ext4/ialloc.c | |
| parent | c8980e1980ccdc2229aa2218d532ddc62e0aabe5 (diff) | |
| download | linux-626b035b816b61a7a7b4d2205a6807e2f11a18c1.tar.gz linux-626b035b816b61a7a7b4d2205a6807e2f11a18c1.tar.bz2 linux-626b035b816b61a7a7b4d2205a6807e2f11a18c1.zip | |
ext4: don't set dioread_nolock by default for blocksize < pagesize
Currently on calling echo 3 > drop_caches on host machine, we see
FS corruption in the guest. This happens on Power machine where
blocksize < pagesize.
So as a temporary workaound don't enable dioread_nolock by default
for blocksize < pagesize until we identify the root cause.
Also emit a warning msg in case if this mount option is manually
enabled for blocksize < pagesize.
Reported-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Signed-off-by: Ritesh Harjani <riteshh@linux.ibm.com>
Link: https://lore.kernel.org/r/20200327200744.12473-1-riteshh@linux.ibm.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/ext4/ialloc.c')
0 files changed, 0 insertions, 0 deletions