public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Vasily Gorbik <gor@linux.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Heiko Carstens <hca@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [GIT PULL] s390 updates for 5.17-rc2
Date: Fri, 28 Jan 2022 12:51:13 +0100	[thread overview]
Message-ID: <your-ad-here.call-01643370673-ext-6058@work.hours> (raw)

Hello Linus,

please pull s390 changes for 5.17-rc2.

Thank you,
Vasily

The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:

  Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-5.17-3

for you to fetch changes up to 663d34c8df98740f1e90241e78e456d00b3c6cad:

  s390/hypfs: include z/VM guests with access control group set (2022-01-26 18:42:39 +0100)

----------------------------------------------------------------
s390 updates for 5.17-rc2

- Fix loading of modules with lots of relocations and add a regression
  test for it.

- Fix machine check handling for vector validity and guarded storage
  validity failures in KVM guests.

- Fix hypervisor performance data to include z/VM guests with access
  control group set.

- Fix z900 build problem in uaccess code.

- Update defconfigs.

----------------------------------------------------------------
Christian Borntraeger (2):
      s390/nmi: handle guarded storage validity failures for KVM guests
      s390/nmi: handle vector validity failures for KVM guests

Heiko Carstens (2):
      s390/uaccess: fix compile error
      s390: update defconfigs

Ilya Leoshkevich (2):
      s390/module: fix loading modules with a lot of relocations
      s390/module: test loading modules with a lot of relocations

Vasily Gorbik (1):
      s390/hypfs: include z/VM guests with access control group set

 arch/s390/Kconfig                    | 15 +++++++++++
 arch/s390/configs/debug_defconfig    | 20 +++++++--------
 arch/s390/configs/defconfig          | 16 +++++++-----
 arch/s390/configs/zfcpdump_defconfig |  3 +++
 arch/s390/hypfs/hypfs_vm.c           |  6 +++--
 arch/s390/include/asm/uaccess.h      |  4 +--
 arch/s390/kernel/module.c            | 37 +++++++++++++-------------
 arch/s390/kernel/nmi.c               | 27 +++++++++++++++----
 arch/s390/lib/Makefile               |  3 +++
 arch/s390/lib/test_modules.c         | 35 +++++++++++++++++++++++++
 arch/s390/lib/test_modules.h         | 50 ++++++++++++++++++++++++++++++++++++
 arch/s390/lib/test_modules_helpers.c | 13 ++++++++++
 12 files changed, 184 insertions(+), 45 deletions(-)
 create mode 100644 arch/s390/lib/test_modules.c
 create mode 100644 arch/s390/lib/test_modules.h
 create mode 100644 arch/s390/lib/test_modules_helpers.c

             reply	other threads:[~2022-01-28 11:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 11:51 Vasily Gorbik [this message]
2022-01-28 17:35 ` [GIT PULL] s390 updates for 5.17-rc2 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=your-ad-here.call-01643370673-ext-6058@work.hours \
    --to=gor@linux.ibm.com \
    --cc=borntraeger@de.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