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]

Date:   Mon, 18 Feb 2019 13:02:09 +0100
From:   Jan Kara <jack@...e.cz>
To:     Meelis Roos <mroos@...ux.ee>
Cc:     "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

On Sun 17-02-19 00:29:40, Meelis Roos wrote:
> > > 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.

Hum, weird. I have hard time understanding how that change could be causing
fs corruption on Aplha but OTOH it is not completely unthinkable. With this
commit we may migrate some block device pages we were not able to migrate
previously and that could be causing some unexpected issue. I'll look into
this.

								Honza
-- 
Jan Kara <jack@...e.com>
SUSE Labs, CR