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.9-rc7
Date: Thu, 2 May 2024 18:26:15 +0200 [thread overview]
Message-ID: <ZjO+p5wo9s16F+hU@tuxmaker.boeblingen.de.ibm.com> (raw)
Hi Linus,
please pull s390 fixes for 6.9-rc7.
Thanks,
Alexander
The following changes since commit d111855ab7ffffc552f6a475259dc392f2319b6d:
s390/mm: Fix NULL pointer dereference (2024-04-17 17:26:34 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-6.9-6
for you to fetch changes up to 7bbe449d0bdb68892cc67e9f5f1bfa106a3588d5:
s390/paes: Reestablish retry loop in paes (2024-05-01 11:52:54 +0200)
----------------------------------------------------------------
s390 updates for 6.9-rc7
- The function __storage_key_init_range() expects the end address to be
the first byte outside the range to be initialized. Fix the callers
that provide the last byte within the range instead.
- 3270 Channel Command Word (CCW) may contain zero data address in case
there is no data in the request. Add data availability check to avoid
erroneous non-zero value as result of virt_to_dma32(NULL) application
in cases there is no data
- Add missing CFI directives for an unwinder to restore the return
address in the vDSO assembler code
- NUL-terminate kernel buffer when duplicating user space memory region
on Channel IO (CIO) debugfs write inject
- Fix wrong format string in zcrypt debug output
- Return -EBUSY code when a CCA card is temporarily unavailabile
- Restore a loop that retries derivation of a protected key from a
secure key in cases the low level reports temporarily unavailability
with -EBUSY code
----------------------------------------------------------------
Bui Quang Minh (1):
s390/cio: Ensure the copied buf is NUL terminated
Claudio Imbrenda (2):
s390/mm: Fix storage key clearing for guest huge pages
s390/mm: Fix clearing storage keys for huge pages
Harald Freudenberger (4):
s390/zcrypt: Fix wrong format string in debug feature printout
s390/zcrypt: Handle ep11 cprb return code
s390/zcrypt: Use EBUSY to indicate temp unavailability
s390/paes: Reestablish retry loop in paes
Jens Remus (1):
s390/vdso: Add CFI for RA register to asm macro vdso_func
Sven Schnelle (1):
s390/3270: Fix buffer assignment
arch/s390/crypto/paes_s390.c | 15 +++++++--
arch/s390/include/asm/dwarf.h | 1 +
arch/s390/kernel/vdso64/vdso_user_wrapper.S | 2 ++
arch/s390/mm/gmap.c | 2 +-
arch/s390/mm/hugetlbpage.c | 2 +-
drivers/s390/char/raw3270.c | 6 ++--
drivers/s390/cio/cio_inject.c | 2 +-
drivers/s390/crypto/zcrypt_ccamisc.c | 6 ++--
drivers/s390/crypto/zcrypt_ep11misc.c | 48 ++++++++++++++++++++++++++++-
9 files changed, 73 insertions(+), 11 deletions(-)
next reply other threads:[~2024-05-02 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 16:26 Alexander Gordeev [this message]
2024-05-02 17:57 ` [GIT PULL] s390 fixes for 6.9-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=ZjO+p5wo9s16F+hU@tuxmaker.boeblingen.de.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).