Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	John David Anglin <dave.anglin@bell.net>
Subject: [GIT PULL] parisc architecture updates for v5.19-rc5
Date: Sat, 2 Jul 2022 19:07:39 +0200	[thread overview]
Message-ID: <YsB7W2GLGRjR+TNr@p100> (raw)

Hi Linus,

please pull two small important fixes for the parisc architecture for v5.19-rc5.

They fix issues with signals in userspace and unaligned memory accesses
in kernel and userspace.

Thanks,
Helge

----

The following changes since commit 03c765b0e3b4cb5063276b086c76f7a612856a9a:

  Linux 5.19-rc4 (2022-06-26 14:22:10 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git tags/for-5.19/parisc-4

for you to fetch changes up to aa78fa905b4431c432071a878da99c2b37fc0e79:

  parisc: Fix vDSO signal breakage on 32-bit kernel (2022-07-02 18:36:58 +0200)

----------------------------------------------------------------
parisc architecture fixes for kernel v5.19-rc5:

Two important fixes for bugs in code which was added in kernel v5.18:

* Fix userspace signal failures on 32-bit kernel due to a bug in vDSO

* Fix 32-bit load-word unalignment exception handler which returned
  wrong values

----------------------------------------------------------------
Helge Deller (2):
      parisc/unaligned: Fix emulate_ldw() breakage
      parisc: Fix vDSO signal breakage on 32-bit kernel

 arch/parisc/kernel/asm-offsets.c | 5 +++++
 arch/parisc/kernel/unaligned.c   | 2 +-
 2 files changed, 6 insertions(+), 1 deletion(-)

             reply	other threads:[~2022-07-02 17:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-02 17:07 Helge Deller [this message]
2022-07-02 17:38 ` [GIT PULL] parisc architecture updates for v5.19-rc5 pr-tracker-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=YsB7W2GLGRjR+TNr@p100 \
    --to=deller@gmx.de \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dave.anglin@bell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --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