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 01:48:10 +0000
Subject: [Bug 200753] write I/O error for inode structure leads to operation
 failure without any warning or error

Theodore Tso ( changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #7 from Theodore Tso ( ---

Before you file more bugs, perhaps you should describe what your model is for
how a file system should behave.  You seem to have some very confused ideas for
how a file system should behave in the face of I/O errors (e.g., thinking that
a symlink to an inode which is in a broken inode table block MUST be a file
system error).

Why don't you write up a document that describes how you think the world works,
because it seems like a waste of your time to create these very careful bug
reports with reproductions when you seem to be operated on a fundamental flawed
model of how a file system behaves, and how it should behave in the face of

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

Powered by blists - more mailing lists