From: Heiko Carstens <hca@linux.ibm.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Christoph Hellwig <hch@lst.de>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [PATCH 0/3] s390: Fix and improve inline assembly constraints
Date: Mon, 2 Mar 2026 14:34:57 +0100 [thread overview]
Message-ID: <20260302133500.1560531-1-hca@linux.ibm.com> (raw)
While looking at xor_xc_2() I realized that its inline assembly constraints
are incorrect. Also the inline assembly constraints for the other xor()
function look incorrect, but are not (execute instruction vs register
zero). However that revealed another real bug on __stackleak_poison() with
another incorrect inline assembly constraint.
Fix and improve all of them.
Heiko Carstens (3):
s390/xor: Fix xor_xc_2() inline assembly constraints
s390/xor: Improve inline assembly constraints
s390/stackleak: Fix __stackleak_poison() inline assembly constraint
arch/s390/include/asm/processor.h | 2 +-
arch/s390/lib/xor.c | 10 +++++-----
2 files changed, 6 insertions(+), 6 deletions(-)
--
2.51.0
next reply other threads:[~2026-03-02 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 13:34 Heiko Carstens [this message]
2026-03-02 13:34 ` [PATCH 1/3] s390/xor: Fix xor_xc_2() inline assembly constraints Heiko Carstens
2026-03-02 15:41 ` Vasily Gorbik
2026-03-02 13:34 ` [PATCH 2/3] s390/xor: Improve " Heiko Carstens
2026-03-02 16:02 ` Vasily Gorbik
2026-03-02 13:35 ` [PATCH 3/3] s390/stackleak: Fix __stackleak_poison() inline assembly constraint Heiko Carstens
2026-03-02 15:40 ` Vasily Gorbik
2026-03-02 13:47 ` [PATCH 0/3] s390: Fix and improve inline assembly constraints Christoph Hellwig
2026-03-02 14:40 ` Heiko Carstens
2026-03-02 16:13 ` Vasily Gorbik
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=20260302133500.1560531-1-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=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.com \
/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