From: Nam Cao <namcao@linutronix.de>
To: Joel Granados <j.granados@samsung.com>
Cc: "Alexandre Ghiti" <alex@ghiti.fr>,
"Mike Rapoport" <rppt@kernel.org>,
"Andreas Dilger" <adilger@dilger.ca>,
"Björn Töpel" <bjorn@kernel.org>,
linux-riscv@lists.infradead.org,
"Thomas Gleixner" <tglx@linutronix.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"ndesaulniers @ google . com" <ndesaulniers@google.com>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Ingo Molnar" <mingo@kernel.org>,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Tejun Heo" <tj@kernel.org>,
"Krister Johansen" <kjlx@templeofstupid.com>,
"Changbin Du" <changbin.du@huawei.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] init: fix allocated page overlapping with PTR_ERR
Date: Fri, 10 May 2024 08:35:44 +0200 [thread overview]
Message-ID: <20240510063544.cAHy0hF8@linutronix.de> (raw)
In-Reply-To: <20240430154238.nu6pebmdlpkxnk7q@joelS2.panther.com>
On Tue, Apr 30, 2024 at 05:42:38PM +0200, Joel Granados wrote:
> On Tue, Apr 30, 2024 at 10:37:59AM +0200, Alexandre Ghiti wrote:
> > The config shows that it is a XIP kernel that comes with its own
> > limitations (text is limited to 32MB for example), so I'm not surprised
> > to see those overlaps.
> >
> > We already discussed the removal of randconfig builds on XIP configs,
> > but IIRC it is not possible.
>
> I just tested this going back until "2023-09-20 602bf1830798 (HEAD)
> Merge branch 'for-6.7' into for-next [Petr Mladek]" and I still saw the
> overlapping errors.
>
> Is this just something that happens always?
Alex is write that this is due to the 32MB size limit on XIP kernel. This
means build failure happens if too many configurations are enabled and the
kernel gets too large.
I just sent a series to lift the size restriction and fix this build failure:
https://lore.kernel.org/lkml/cover.1715286093.git.namcao@linutronix.de/
Best regards,
Nam
prev parent reply other threads:[~2024-05-10 6:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 10:29 [PATCH] init: fix allocated page overlapping with PTR_ERR Nam Cao
2024-04-18 10:54 ` Mike Rapoport
2024-04-18 11:12 ` Nam Cao
2024-04-18 12:41 ` Björn Töpel
2024-04-18 13:01 ` Nam Cao
2024-04-18 13:07 ` Nam Cao
[not found] ` <CGME20240429125236eucas1p24219f2d332e0267794a2f87dea9f39c4@eucas1p2.samsung.com>
2024-04-29 12:52 ` Joel Granados
2024-04-30 7:31 ` Nam Cao
2024-04-30 8:37 ` Alexandre Ghiti
2024-04-30 13:35 ` Joel Granados
2024-04-30 15:42 ` Joel Granados
2024-05-10 6:35 ` Nam Cao [this message]
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=20240510063544.cAHy0hF8@linutronix.de \
--to=namcao@linutronix.de \
--cc=adilger@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=arnd@arndb.de \
--cc=bjorn@kernel.org \
--cc=changbin.du@huawei.com \
--cc=christophe.leroy@csgroup.eu \
--cc=geert+renesas@glider.be \
--cc=j.granados@samsung.com \
--cc=kjlx@templeofstupid.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mcgrof@kernel.org \
--cc=mingo@kernel.org \
--cc=ndesaulniers@google.com \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).