From: Alexander Gordeev <agordeev@linux.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] s390 fixes for 6.17-rc3
Date: Fri, 22 Aug 2025 14:36:08 +0200 [thread overview]
Message-ID: <20250822123608.142112A72-agordeev@linux.ibm.com> (raw)
Hi Linus,
please pull s390 fixes for 6.17-rc3.
Thanks,
Alexander
The following changes since commit c17b750b3ad9f45f2b6f7e6f7f4679844244f0b9:
Linux 6.17-rc2 (2025-08-17 15:22:10 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-6.17-3
for you to fetch changes up to 3868f910440c47cd5d158776be4ba4e2186beda7:
s390/hypfs: Enable limited access during lockdown (2025-08-21 17:46:14 +0200)
----------------------------------------------------------------
s390 fixes for 6.17-rc3
- When kernel lockdown is active userspace tools that rely on read
operations only are unnecessarily blocked. Fix that by avoiding
ioctl registration during lockdown
- Invalid NULL pointer accesses succeed due to the lowcore is always
mapped the identity mapping pinned to zero. To fix that never map
the first two pages of physical memory with identity mapping
- Fix invalid SCCB present check in the SCLP interrupt handler
- Update defconfigs
----------------------------------------------------------------
Heiko Carstens (3):
s390/configs: Update defconfigs
s390/configs: Set HZ=1000
s390/mm: Do not map lowcore with identity mapping
Peter Oberparleiter (3):
s390/sclp: Fix SCCB present check
s390/hypfs: Avoid unnecessary ioctl registration in debugfs
s390/hypfs: Enable limited access during lockdown
arch/s390/boot/vmem.c | 3 +++
arch/s390/configs/debug_defconfig | 33 ++++++++++++++++-----------------
arch/s390/configs/defconfig | 34 +++++++++++++++-------------------
arch/s390/configs/zfcpdump_defconfig | 3 ++-
arch/s390/hypfs/hypfs_dbfs.c | 19 ++++++++++++-------
drivers/s390/char/sclp.c | 11 +++++++++--
6 files changed, 57 insertions(+), 46 deletions(-)
next reply other threads:[~2025-08-22 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 12:36 Alexander Gordeev [this message]
2025-08-22 14:18 ` pr-tracker-bot
2025-10-01 22:44 ` Thomas Weißschuh
2025-10-02 11:05 ` Heiko Carstens
2025-10-02 14:43 ` Heiko Carstens
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=20250822123608.142112A72-agordeev@linux.ibm.com \
--to=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@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
all inboxes | Powered by JetHome®