linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Linux kernel regression tracking (#update)"  <regressions@leemhuis.info>
To: Jorropo <jorropo.pgm@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	regressions@lists.linux.dev, nborisov@suse.com,
	Matthew Wilcox <willy@infradead.org>
Subject: Re: [REGRESSION] XArray commit prevents booting with 6.0-rc1 or later
Date: Thu, 5 Jan 2023 09:23:27 +0100	[thread overview]
Message-ID: <311733fe-cd0d-5afb-b189-835d9ab92aa2@leemhuis.info> (raw)
In-Reply-To: <f2ff04c7-fbae-6343-a9cb-10a9c681463b@leemhuis.info>

On 12.12.22 08:03, Thorsten Leemhuis wrote:
> On 28.11.22 13:18, Matthew Wilcox wrote:
>> On Sun, Nov 20, 2022 at 12:20:13AM +0100, Jorropo wrote:
>>> Matthew Wilcox <willy@infradead.org> wrote :
>>>> On Sat, Nov 19, 2022 at 05:07:45AM +0100, Jorropo wrote:
>>>>>
>>>>> 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 rebuilt both 1dd685c414a7b9fdb3d23aca3aedae84f0b998ae and
>>> the parent commit (v5.19-rc6), then tried to start each one 8 times
>>> (shuffled in a Thue morse sequence).
>>> 0 successes for 1dd685c414a7b9fdb3d23aca3aedae84f0b998ae
>>> 8 successes for v5.19-rc6
>>>
>>> This really does not look like an intermittent issue.
>>
>> OK, you convinced me.  Can you boot 1dd685c414 with the command line
>> parameters "debug initcall_debug" so we get more information?
> 
> Jorropo, did you ever provide the information Matthew asked for? I'm
> asking, as this looks stalled -- and I wonder why. Or was progress made
> somewhere and I just missed it?

For the record: Jorropo sent me a private mail where he states "this is
some installation issue because after some updates the previous release
that used to work does not anymore. You can close this.". Hence:

#regzbot resolve: not a regression according to the reporter

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.

  reply	other threads:[~2023-01-05  8:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19  4:07 [REGRESSION] XArray commit prevents booting with 6.0-rc1 or later Jorropo
2022-11-19  6:21 ` Matthew Wilcox
2022-11-19 23:20   ` Jorropo
2022-11-28 12:18     ` Matthew Wilcox
2022-12-12  7:03       ` Thorsten Leemhuis
2023-01-05  8:23         ` Linux kernel regression tracking (#update) [this message]
2022-11-21  8:58 ` [REGRESSION] XArray commit prevents booting with 6.0-rc1 or later #forregzbot Thorsten Leemhuis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=311733fe-cd0d-5afb-b189-835d9ab92aa2@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=jorropo.pgm@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nborisov@suse.com \
    --cc=regressions@lists.linux.dev \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).