| 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
| ||
|
Message-ID: <bug-201685-13602-MYeU74AAh8@https.bugzilla.kernel.org/> Date: Fri, 30 Nov 2018 12:10:27 +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 #86 from Rainer Fiebig (jrf@...lbox.org) --- (In reply to Hao Wei Tee from comment #85) > (In reply to Rainer Fiebig from comment #83) > > Interesting idea. But what works in one direction might not necessarily > work > > the other way round. > > Exactly my point. We know that (4.19 ext4 and kernel is broken), (4.18 ext4 > and kernel is working), and (4.18 ext4 and 4.19 kernel is working). > > If (4.19 ext4 and 4.18 kernel) is broken, then _most likely_ the bug is > caused by something that changed in v4.18..v4.19. If (4.19 ext4 and 4.18 > kernel) *works*, then either the bug is in something else that changed, or > there is an interaction between two changes that happened in v4.18..v4.19. > Sure, I understand this. I would just shy away from recommending this to others without a nod from higher powers. But of course it's up to Nestor whether he wants to try this or not. > In any case, bisecting v4.18..v4.19 will probably give us a clue. Let's hope for the best. Perhaps bisecting fs/ext4 will provide enough of a clue already and spare the poor bisecter to have to bisect the whole beast. ;) -- You are receiving this mail because: You are watching the assignee of the bug.
Powered by blists - more mailing lists