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:   Sun, 10 May 2020 20:37:42 +0000
Subject: [Bug 207635] EXT4-fs error (device sda3): ext4_lookup:1701: inode
 #...: comm find: casefold flag without casefold feature; EXT4-fs (sda3):
 Remounting filesystem read-only

Joerg M. Sigle ( changed:

           What    |Removed                     |Added
     Kernel Version|5.5.11, 5.5.10              |5.4.20, 5.5.10, 5.5.11,
                   |                            |5.6.11

--- Comment #2 from Joerg M. Sigle ( ---
After upgrade to 5.6.11, once again had the root filesystem become read only.

I'm now going back to 5.3.15 which may have been the last unproblematic version
I tried - just to verify once more that the problem doesn't occur with that
older version.

N.B.: Googling "casefold flag without casefold feature" returned a patch - and
most probably, the same problem for someone else in Kernel 5.4 vs. 5.3:
> ext4: fix kernel oops caused by spurious casefold flag
> 5.4.20: EXT4-fs error (device mmcblk0p1): ext4_lookup:1700: inode #4950: comm
> rsync: casefold flag without casefold feature
> 5.3.9: without error 

So the problem may have been adressed - but that was in 2019; I'm wondering how
it could still be there in May 2020 kernels?

You are receiving this mail because:
You are watching the assignee of the bug.

Powered by blists - more mailing lists