From: Greg KH <gregkh@linuxfoundation.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Sasha Levin <sashal@kernel.org>,
David Laight <David.Laight@aculab.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [regression] linux-6.6.y, minmax: virtual memory exhausted in i586 chroot during kernel compilation
Date: Tue, 13 Feb 2024 15:50:00 +0100 [thread overview]
Message-ID: <2024021318-shifty-daybed-fca8@gregkh> (raw)
In-Reply-To: <f9f89284-0f48-4971-ad8d-86938a82fafc@leemhuis.info>
On Mon, Feb 12, 2024 at 05:16:58PM +0100, Linux regression tracking (Thorsten Leemhuis) wrote:
> Hi Greg, Sasha, and David,
>
> I noticed a regression report in bugzilla.kernel.org that seems to be
> specific to the linux-6.6.y series:
>
> Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=218484 :
>
> > After upgrading to version 6.6.16, the kernel compilation on a i586
> > arch (on a 32bit chroot in a 64bit host) fails with a message:
> >
> > virtual memory exhausted: Cannot allocate memory
> >
> > this happens even lowering the number of parallel compilation
> > threads. On a x86_64 arch the same problem doesn't occur. It's not
> > clear whether some weird recursion is triggered that exhausts the
> > memory, but it seems that the problem is caused by the patchset
> > 'minmax' added to the 6.6.16 version, in particular it seems caused
> > by these patches:
> >
> > - minmax-allow-min-max-clamp-if-the-arguments-have-the-same-signedness.patch
> > - minmax-fix-indentation-of-__cmp_once-and-__clamp_once.patch
> > - minmax-allow-comparisons-of-int-against-unsigned-char-short.patch
> > - minmax-relax-check-to-allow-comparison-between-unsigned-arguments-and-signed-constants.patch
> >
> > Reverting those patches fixes the memory exhaustion problem during compilation.
>
> The reporter later added:
>
> > From a quick test the same problem doesn't occur in 6.8-rc4.
> See the ticket for more details.
>
> Note, you have to use bugzilla to reach the reporter, as I sadly[1] can
> not CCed them in mails like this.
>
> [TLDR for the rest of this mail: I'm adding this report to the list of
> tracked Linux kernel regressions; the text you find below is based on a
> few templates paragraphs you might have encountered already in similar
> form.]
>
> BTW, let me use this mail to also add the report to the list of tracked
> regressions to ensure it's doesn't fall through the cracks:
>
> #regzbot introduced: 204c653d5d0c79940..9487d93f172acef
> https://bugzilla.kernel.org/show_bug.cgi?id=218484
> #regzbot title: minmax: virtual memory exhausted in 6.6.16 with i586 chroot
> #regzbot ignore-activity
>
> 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
> If I did something stupid, please tell me, as explained on that page.
>
> [1] because bugzilla.kernel.org tells users upon registration their
> "email address will never be displayed to logged out users"
I think this was already fixed in 6.7 or Linus's tree, but I can't seem
to find the commit at the moment.
What file is causing the compiler to crash? Is it some video or media
driver?
thanks,
greg k-h
next prev parent reply other threads:[~2024-02-13 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 16:16 [regression] linux-6.6.y, minmax: virtual memory exhausted in i586 chroot during kernel compilation Linux regression tracking (Thorsten Leemhuis)
2024-02-13 14:50 ` Greg KH [this message]
2024-02-13 15:01 ` Linux regression tracking (Thorsten Leemhuis)
2024-02-13 15:09 ` Greg KH
2024-02-13 15:13 ` David Laight
2024-02-13 16:05 ` Greg KH
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=2024021318-shifty-daybed-fca8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=David.Laight@aculab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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