From: sashiko-bot@kernel.org
To: "Heiko Carstens" <hca@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, "Vasily Gorbik" <gor@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>
Subject: Re: [PATCH v2 1/2] s390/signal: Fix incorrect return address in signal frame
Date: Tue, 13 Oct 2026 13:43:56 +0000 [thread overview]
Message-ID: <sashiko-outbox-169849@kernel.org> (raw)
In-Reply-To: <20261013133453.2288894-2-hca@linux.ibm.com>
> exit_to_user_mode_loop() can call arch_do_signal_or_restart() multiple
> times when signals are pending.
>
> If the first call set up a vDSO system call restart by saving the real
> user return address and adjusting psw.addr so it points to the vDSO stub,
> a second call builds the signal frame with the wrong return address.
>
> Restore psw.addr from arch_data, and set the return code to -EINTR before
> building the signal frame.
>
> This requires restart_block.arch_data to be properly initialized for all
> tasks. Move the initialization in copy_thread() in front of the kernel
> thread check, so that it also covers kernel threads and their children
> (PID 1, usermode helpers). Only PID 0 is left uninitialized, since it
> never returns to user space.
>
> Fixes: df29a7440c4b ("s390/signal: switch to using vdso for sigreturn and syscall restart")
> Cc: stable@vger.kernel.org
> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261013133453.2288894-1-hca@linux.ibm.com?part=1
next prev parent reply other threads:[~2026-10-13 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 13:34 [PATCH v2 0/2] s390/signal: Fix return address handling + cleanup Heiko Carstens
2026-10-13 13:34 ` [PATCH v2 1/2] s390/signal: Fix incorrect return address in signal frame Heiko Carstens
2026-10-13 13:43 ` sashiko-bot [this message]
2026-10-13 13:34 ` [PATCH v2 2/2] s390/signal: Cleanup coding style Heiko Carstens
2026-10-13 13:49 ` sashiko-bot
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=sashiko-outbox-169849@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.