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.7-rc3
Date: Sun, 26 Nov 2023 18:04:41 +0100 [thread overview]
Message-ID: <ZWN6qUkUEewrKNOe@p100> (raw)
Hi Linus,
this patchset fixes and enforces correct section alignments for the ex_table,
altinstructions, parisc_unwind, jump_table and bug_table which are created by
inline assembly.
Due to not being correctly aligned at link & load time they can trigger
unnecessarily the kernel unaligned exception handler at runtime.
While at it, I switched the bug table to use relative addresses which reduces
the size of the table by half on 64-bit.
We still had the ENOSYM and EREMOTERELEASE errno symbols as left-overs from
HP-UX, which now trigger build-issues with glibc. We can simply remove them.
Most of the patches are tagged for stable kernel series.
Please pull.
Thanks!
Helge
----------------------------------------------------------------
The following changes since commit 98b1cc82c4affc16f5598d4fa14b1858671b2263:
Linux 6.7-rc2 (2023-11-19 15:02:14 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git tags/parisc-for-6.7-rc3
for you to fetch changes up to 43266838515d30dc0c45d5c7e6e7edacee6cce92:
parisc: Reduce size of the bug_table on 64-bit kernel by half (2023-11-25 09:43:18 +0100)
----------------------------------------------------------------
parisc architecture fixes for kernel v6.7-rc3:
- Drop HP-UX ENOSYM and EREMOTERELEASE return codes to avoid glibc
build issues
- Fix section alignments for ex_table, altinstructions, parisc unwind
table, jump_table and bug_table
- Reduce size of bug_table on 64-bit kernel by using relative
pointers
----------------------------------------------------------------
Helge Deller (9):
parisc: Mark ex_table entries 32-bit aligned in assembly.h
parisc: Mark ex_table entries 32-bit aligned in uaccess.h
parisc: Mark altinstructions read-only and 32-bit aligned
parisc: Mark jump_table naturally aligned
parisc: Mark lock_aligned variables 16-byte aligned on SMP
parisc: Ensure 32-bit alignment on parisc unwind section
parisc: Use natural CPU alignment for bug_table
parisc: Drop the HP-UX ENOSYM and EREMOTERELEASE error codes
parisc: Reduce size of the bug_table on 64-bit kernel by half
arch/parisc/Kconfig | 7 ++++--
arch/parisc/include/asm/alternative.h | 9 ++++---
arch/parisc/include/asm/assembly.h | 1 +
arch/parisc/include/asm/bug.h | 38 +++++++++++++++++-------------
arch/parisc/include/asm/jump_label.h | 8 +++++--
arch/parisc/include/asm/ldcw.h | 2 +-
arch/parisc/include/asm/uaccess.h | 1 +
arch/parisc/include/uapi/asm/errno.h | 2 --
arch/parisc/kernel/vmlinux.lds.S | 1 +
lib/errname.c | 6 -----
tools/arch/parisc/include/uapi/asm/errno.h | 2 --
11 files changed, 43 insertions(+), 34 deletions(-)
next reply other threads:[~2023-11-26 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 17:04 Helge Deller [this message]
2023-11-26 18:03 ` [GIT PULL] parisc architecture fixes for v6.7-rc3 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=ZWN6qUkUEewrKNOe@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