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-L738sOFqW5@https.bugzilla.kernel.org/>
Date:   Wed, 28 Nov 2018 05:05:40 +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 #59 from Theodore Tso (tytso@....edu) ---
Created attachment 279687
  --> https://bugzilla.kernel.org/attachment.cgi?id=279687&action=edit
Ext4 from 4.18

I'm pretty sure the problem is not in the ext4 changes between 4.18 and 4.19,
since the changes are all quite innocuous (and if it was in the ext4 code, the
regression testing really should have picked it up).

But just to rule things out, I've uploaded the contents of fs/ext4 from 4.18.  
I've verified it can be transplanted on top of 4.19 kernel.   Could the people
who are experiencing problems with 4.19 try building a kernel with the 4.18
fs/ext4 directory?   If you still see problems, then the problem has to be
elsewhere.   If you don't, then we can take a closer look at the ext4 changes
(although I'd then be really puzzled why it's only showing up for some folks,
but not others).

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