From: Heiko Carstens <hca@linux.ibm.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
linux-s390@vger.kernel.org, lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: next-20250616: S390 gcc-8 allnoconfig mm mempool.c In function remove_element
Date: Mon, 16 Jun 2025 16:08:58 +0200 [thread overview]
Message-ID: <20250616140858.9423D47-hca@linux.ibm.com> (raw)
In-Reply-To: <CA+G9fYuu5r34=bndUYWNxe_yLgBaPGXmK9WP3WTtoXMs_2LX-Q@mail.gmail.com>
On Mon, Jun 16, 2025 at 07:06:10PM +0530, Naresh Kamboju wrote:
> On Mon, 16 Jun 2025 at 17:36, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >
> > Regression while building S390 with the Linux next-20250616
> > with gcc-8 the following kernel warnings found.
> >
> > Regressions found on S390
> > - build/gcc-8-lkftconfig-allnoconfig
> > - build/gcc-8-lkftconfig-hardening
> >
> > Regression Analysis:
> > - New regression? Yes
> > - Reproducibility? Yes
> >
> > First seen on the next-20250616
> > Good: next-20250613
> > Bad: next-20250616
> >
> > Build regression: S390 gcc-8 allnoconfig mm mempool.c In function remove_element
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> >
> > ## Build errors
> > mm/mempool.c: In function 'remove_element':
> > include/linux/compiler_types.h:497:20: warning: asm operand 0 probably
> > doesn't match constraints
> > #define asm_inline asm __inline
> > ^~~
> > arch/s390/include/asm/bug.h:12:2: note: in expansion of macro 'asm_inline'
> > asm_inline volatile( \
> > ^~~~~~~~~~
> > arch/s390/include/asm/bug.h:43:2: note: in expansion of macro '__EMIT_BUG'
> > __EMIT_BUG("", 0); \
> > ^~~~~~~~~~
> > include/asm-generic/bug.h:77:57: note: in expansion of macro 'BUG'
> > #define BUG_ON(condition) do { if (unlikely(condition)) BUG(); } while (0)
> > ^~~
> > mm/mempool.c:149:2: note: in expansion of macro 'BUG_ON'
> > BUG_ON(pool->curr_nr < 0);
> > ^~~~~~
> > include/linux/compiler_types.h:497:20: error: impossible constraint in 'asm'
> > #define asm_inline asm __inline
> > ^~~
>
> Anders bisect this build regressions and found,
>
> # first bad commit:
> [45c79ca947c936085c94b716be92eaf9a1bdc8bb]
> bugs/s390: Use 'cond_str' in __EMIT_BUG()
I'll take a look at this tomorrow. I guess the easiest "fix" is to
change the s390 bug code similar to arm64, so that those problems with
inline asm constraints cannot happen anymore.
At least I hope that will work. We'll see.
prev parent reply other threads:[~2025-06-16 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 12:06 Naresh Kamboju
2025-06-16 13:36 ` Naresh Kamboju
2025-06-16 14:08 ` Heiko Carstens [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=20250616140858.9423D47-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=gor@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mingo@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
/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
all inboxes | Powered by JetHome®