linux-kernel - Re: ext4 corruption on alpha with 4.20.0-09062-gd8372ba8ce28

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: <e175b885-082a-97c1-a0be-999040a06443@linux.ee>
Date:   Sun, 17 Feb 2019 00:29:40 +0200
From:   Meelis Roos <mroos@...ux.ee>
To:     "Theodore Y. Ts'o" <tytso@....edu>, linux-alpha@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>, linux-block@...r.kernel.org,
        Jan Kara <jack@...e.cz>
Subject: Re: ext4 corruption on alpha with 4.20.0-09062-gd8372ba8ce28

>> The result of the bisection is
>> [88dbcbb3a4847f5e6dfeae952d3105497700c128] blkdev: avoid migration stalls for blkdev pages
>>
>> Is that result relevant for the problem or should I continue bisecting between 4.20.0 and the so far first bad commit?
> 
> Can you try reverting the commit and see if it makes the problem go away?

Tried reverting it on top of 5.0.0-rc6-00153-g5ded5871030e and it seems to make the kernel work - emerge --sync succeeded.

Unfinished further bisection has also not yielded any other bad revisions so far.

-- 
Meelis Roos