All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramin Moussavi <lordrasmus@gmail.com>
To: Michal Simek <monstr@monstr.eu>
Cc: linux-kernel@vger.kernel.org, Ramin Moussavi <lordrasmus@gmail.com>
Subject: [PATCH 0/2] microblaze: fix signal-frame handling for NPTL
Date: Thu,  4 Jun 2026 17:37:10 +0200	[thread overview]
Message-ID: <cover.1780587199.git.lordrasmus@gmail.com> (raw)

Two independent fixes to the microblaze signal-delivery path, both found
while bringing the uClibc-ng NPTL test suite up on microblazeel under
qemu-system (petalogix-s3adsp1800).

Patch 1 wires up sigaltstack(), which is currently routed to
sys_ni_syscall even though the signal code fully supports an alternate
stack - microblaze is the only architecture leaving it unimplemented.

Patch 2 reserves the ABI argument-home area at the top of the signal
frame.  The MicroBlaze calling convention lets a handler store its
incoming register arguments into [r1+4]..[r1+28]; since r1 points at
struct rt_sigframe on entry, those stores land in siginfo/ucontext and
corrupt the signal state.  An eight-word leading gap moves them into
scratch space.

Both were tested with the uClibc-ng NPTL tests; the affected tests
(tst-cancel20/21, tst-cancelx20/21, tst-signal6, tst-timer4/5,
tst-mqueue5) now pass.  checkpatch --strict is clean and both apply to
current linux-next.

Ramin Moussavi (2):
  microblaze: wire up sigaltstack
  microblaze: reserve the ABI argument-home area in the signal frame

 arch/microblaze/kernel/signal.c             | 7 +++++++
 arch/microblaze/kernel/syscalls/syscall.tbl | 2 +-
 2 files changed, 8 insertions(+), 1 deletion(-)

-- 
2.53.0


             reply	other threads:[~2026-06-04 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 15:37 Ramin Moussavi [this message]
2026-06-04 15:37 ` [PATCH 1/2] microblaze: wire up sigaltstack Ramin Moussavi
2026-06-04 15:37 ` [PATCH 2/2] microblaze: reserve the ABI argument-home area in the signal frame Ramin Moussavi

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=cover.1780587199.git.lordrasmus@gmail.com \
    --to=lordrasmus@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monstr@monstr.eu \
    /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.