linux-ext4 - [Bug 201685] ext4 file system corruption

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-201685-13602-QHTM1shKUH@https.bugzilla.kernel.org/>
Date:   Tue, 04 Dec 2018 20:59:49 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 201685] ext4 file system corruption

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

--- Comment #240 from Guenter Roeck (linux@...ck-us.net) ---
As mentioned earlier, I only ever saw the problem on two of four systems (see
#57), all running the same kernel and the same version of Ubuntu. The only
differences are mainboard, CPU, and attached drive types.

I don't think we know for sure what it takes to trigger the problem. We have
seen various guesses, from gcc version to l1tf mitigation to CPU type, broken
hard drives, and whatnot. At this time evidence points to the block subsystem,
with bisect pointing to a commit which relies on the state of the HW queue
(empty or not) in conjunction with the 'none' io scheduler. This may suggest
that drive speed and access timing may be involved. That guess may of course be
just as wrong as all the others.

Let's just hope that Jens will be able to track down and fix the problem. Then
we may be able to get a better idea what it actually takes to trigger it.

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