linux-ext4 - [Bug 200753] write I/O error for inode structure leads to operation failure without any warning or error

lists.openwall.net		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]

Message-ID: <bug-200753-13602-OCpLtA51vL@https.bugzilla.kernel.org/>
Date:   Tue, 07 Aug 2018 01:48:10 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...nel.org
Subject: [Bug 200753] write I/O error for inode structure leads to operation
 failure without any warning or error

https://bugzilla.kernel.org/show_bug.cgi?id=200753

Theodore Tso (tytso@....edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tytso@....edu

--- Comment #7 from Theodore Tso (tytso@....edu) ---
Shehbaz,

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
errors.

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