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-NWXjqJIuoF@https.bugzilla.kernel.org/>
Date:   Tue, 07 Aug 2018 00:52:29 +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

Eric Sandeen (sandeen@...deen.net) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sandeen@...deen.net

--- Comment #6 from Eric Sandeen (sandeen@...deen.net) ---
A couple things up front; an IO error should not in general lead to a fsck
error, and it doesn't require a kernel message.  So "no error reported in fsck
or kernelspace" isn't a bug.

However, failed syscalls should return errors to the user.  Are you saying that
they do not do so?

As this appears to be a complex test to set up, can you perhaps include the
strace of one or more of these failing operations on your prepared device?

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