linux-kernel - Re: [REGRESSION] XArray commit prevents booting with 6.0-rc1 or later

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: <Y3h118oIDsvclZHM@casper.infradead.org>
Date:   Sat, 19 Nov 2022 06:21:11 +0000
From:   Matthew Wilcox <willy@...radead.org>
To:     Jorropo <jorropo.pgm@...il.com>
Cc:     linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        nborisov@...e.com, regressions@...ts.linux.dev,
        stable@...r.kernel.org
Subject: Re: [REGRESSION] XArray commit prevents booting with 6.0-rc1 or later

On Sat, Nov 19, 2022 at 05:07:45AM +0100, Jorropo wrote:
> #regzbot introduced v5.19-rc6..1dd685c414a7b9fdb3d23aca3aedae84f0b998ae
> 
> Hi, I recently tried to upgrade to linux v6.0.x but when trying to
> boot it fails with "error: out of memory" when or after loading
> initramfs (which then kpanics because the vfs root is missing).
> The latest releases I tested are v6.0.9 and v6.1-rc5 and it's broken there too.
> 
> I bisected the error to this patch:
> 1dd685c414a7b9fdb3d23aca3aedae84f0b998ae "XArray: Add calls to
> might_alloc()" is the first bad commit.
> I've confirmed this is not a side effect of a poor bitsect because
> 1dd685c414a7b9fdb3d23aca3aedae84f0b998ae~1 (v5.19-rc6) works.

That makes no sense.  I can't look into this until Wednesday, but I
suggest that what you have is an intermittent failure to boot, and
the bisect has led you down the wrong path.

> I've tried reverting the failing commit on top of v6.0.9 and it didn't fixed it.
> 
> My system is:
> CPU: Ryzen 3600
> Motherboard: B550 AORUS ELITE V2
> Ram: 48GB (16+32) of unmatched DDR4
> GPU: AMD rx580
> Various ssds, hdds and network cards plugged with various buses.
> 
> You can find a folder with my .config, bisect logs and screenshots of
> the error messages there:
> https://jorropo.net/ipfs/QmaWH84UPEen4E9n69KZiLjPDaTi2aJvizv3JYiL7Gfmnr/
> https://ipfs.io/ipfs/QmaWH84UPEen4E9n69KZiLjPDaTi2aJvizv3JYiL7Gfmnr/
> 
> I'll be happy to assist you if you need help reproducing this issue
> and or testing fixes.
> 
> Thx, Jorropo