All of lore.kernel.org
 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 fixes for v6.2-rc7
Date: Sat, 4 Feb 2023 15:40:45 +0100	[thread overview]
Message-ID: <Y95ubeJ0b96rw/rS@p100> (raw)

Hi Linus,

please pull some small fixes for the parisc architecture, 3 out of 4 are
tagged for stable series.

The most important patch fixes ptrace() for the compat case, which is
used by latest strace source which now used PTRACE_GETREGS() to get the
CPU registers.

Thanks,
Helge


The following changes since commit b7bfaa761d760e72a969d116517eaa12e404c262:

  Linux 6.2-rc3 (2023-01-08 11:49:43 -0600)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git tags/parisc-for-6.2-rc7

for you to fetch changes up to 316f1f42b5cc1d95124c1f0387c867c1ba7b6d0e:

  parisc: Wire up PTRACE_GETREGS/PTRACE_SETREGS for compat case (2023-02-01 21:42:37 +0100)

----------------------------------------------------------------
parisc architecture fixes for kernel v6.2-rc7:

- Fix PTRACE_GETREGS/PTRACE_SETREGS for 32-bit userspace on 64-bit kernel
- pdc_iodc_print() dropped chars for newline in strings
- Drop constants in favour of PRIV_USER
- use safer strscpy() function in pdc_stable driver

----------------------------------------------------------------
Helge Deller (3):
      parisc: Fix return code of pdc_iodc_print()
      parisc: Replace hardcoded value with PRIV_USER constant in ptrace.c
      parisc: Wire up PTRACE_GETREGS/PTRACE_SETREGS for compat case

Xu Panda (1):
      parisc: pdc_stable: use strscpy() to instead of strncpy()

 arch/parisc/kernel/firmware.c |  5 +++--
 arch/parisc/kernel/ptrace.c   | 21 ++++++++++++++++-----
 drivers/parisc/pdc_stable.c   |  9 +++------
 3 files changed, 22 insertions(+), 13 deletions(-)

             reply	other threads:[~2023-02-04 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-04 14:40 Helge Deller [this message]
2023-02-04 19:55 ` [GIT PULL] parisc architecture fixes for v6.2-rc7 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=Y95ubeJ0b96rw/rS@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 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.