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  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:   Tue, 07 Aug 2018 15:02:10 +0000
Subject: [Bug 200753] write I/O error for inode structure leads to operation
 failure without any warning or error

--- Comment #13 from Eric Sandeen ( ---
To some of Ted's point, I agree and was going to make a similar observation - a
real disk error would have led to /some/ error message from somewhere lower in
teh stack, whether from the scsi layer, lvm, or whatever.  If the custom dm
target here silently returns an error, that's different behavior than you'd
typically see upstream.

It leave the open question of "should ext4 printk something as well" but in the
real world it'd be much more surprising to see a completely silent EIO from

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

Powered by blists - more mailing lists