From: Heiko Carstens <hca@linux.ibm.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-arch@vger.kernel.org, Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH 16/15] bugs/s390: Use in 'cond_str' to __EMIT_BUG()
Date: Mon, 9 Jun 2025 17:56:57 +0200 [thread overview]
Message-ID: <20250609155657.8183A92-hca@linux.ibm.com> (raw)
In-Reply-To: <aEabAPB5Y9EbSPkt@gmail.com>
On Mon, Jun 09, 2025 at 10:27:44AM +0200, Ingo Molnar wrote:
> So I'm not sure what happened: I tried to reproduce what I did
> originally, but my naive patch ran into assembler build errors when a
> WARN_ON() macro tried to use the '%' C operator, such as
> fs/crypto/crypto.c:123:
>
> include/linux/compiler_types.h:497:20: error: invalid 'asm': invalid %-code
> arch/s390/include/asm/bug.h:12:2: note: in expansion of macro 'asm_inline'
> arch/s390/include/asm/bug.h:50:2: note: in expansion of macro '__EMIT_BUG'
> include/asm-generic/bug.h:119:3: note: in expansion of macro '__WARN_FLAGS'
> fs/crypto/crypto.c:123:6: note: in expansion of macro 'WARN_ON_ONCE'
>
> Which corresponds to:
>
> if (WARN_ON_ONCE(len % FSCRYPT_CONTENTS_ALIGNMENT != 0))
> return -EINVAL;
>
> I'm quite sure I never saw these build errors - I saw linker errors
> related to the u16 overflow I documented in the changelog. (Note to
> self: copy & paste more of the build error context next time around.)
>
> Your version doesn't have that build problem, so I picked it up with
> the changelog below and your Signed-off-by. Does that look good to you?
Yes, fine with me.
prev parent reply other threads:[~2025-06-09 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250515124644.2958810-1-mingo@kernel.org>
2025-05-15 12:46 ` [PATCH 10/15] bugs/s390: Pass in 'cond_str' to __EMIT_BUG() Ingo Molnar
2025-05-20 13:39 ` Heiko Carstens
2025-06-09 8:27 ` [PATCH 16/15] bugs/s390: Use " Ingo Molnar
2025-06-09 15:56 ` 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=20250609155657.8183A92-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=svens@linux.ibm.com \
--cc=torvalds@linux-foundation.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).