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>,
Sven Schnelle <svens@stackframe.org>
Subject: [GIT PULL] parisc architecture bug and warning fixes for kernel v5.16-rc3
Date: Wed, 24 Nov 2021 18:07:50 +0100 [thread overview]
Message-ID: <YZ5xZijH8L7IIpJh@ls3530> (raw)
The following changes since commit 136057256686de39cc3a07c2e39ef6bc43003ff6:
Linux 5.16-rc2 (2021-11-21 13:47:39 -0800)
are available in the Git repository at:
http://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git tags/for-5.16/parisc-5
for you to fetch changes up to 98400ad75e95860e9a10ec78b0b90ab66184a2ce:
Revert "parisc: Fix backtrace to always include init funtion names" (2021-11-22 07:37:31 +0100)
----------------------------------------------------------------
parisc bug and warning fixes for kernel v5.16-rc3
Increase the FRAME_WARN value to avoid some new warnings which showed up
in the Linux kernel test project, revert a patch which moved the _stext
symbol and thus tiggered errors in the hardened usercopy checks, and
introduce an extru_safe() assembler macro to overcome possible unsafe
usage of the extru asm statement on 64-bit PA2.0 machines.
----------------------------------------------------------------
Helge Deller (4):
parisc: Increase FRAME_WARN to 2048 bytes on parisc
parisc: Provide an extru_safe() macro to extract unsigned bits
parisc: Convert PTE lookup to use extru_safe() macro
Revert "parisc: Fix backtrace to always include init funtion names"
John David Anglin (1):
parisc: Fix extraction of hash lock bits in syscall.S
arch/parisc/include/asm/assembly.h | 11 +++++++++++
arch/parisc/kernel/entry.S | 14 +++-----------
arch/parisc/kernel/syscall.S | 4 ++--
arch/parisc/kernel/vmlinux.lds.S | 3 +--
lib/Kconfig.debug | 5 +++--
5 files changed, 20 insertions(+), 17 deletions(-)
next reply other threads:[~2021-11-24 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 17:07 Helge Deller [this message]
2021-11-24 18:31 ` 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=YZ5xZijH8L7IIpJh@ls3530 \
--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=svens@stackframe.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
all inboxes | Powered by JetHome®