From: Vasily Gorbik <gor@linux.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Alexander Gordeev <agordeev@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 6.0-rc3
Date: Sat, 27 Aug 2022 12:07:59 +0200 [thread overview]
Message-ID: <your-ad-here.call-01661594879-ext-8999@work.hours> (raw)
Hello Linus,
please pull s390 changes for 6.0-rc3.
Thank you,
Vasily
The following changes since commit 1c23f9e627a7b412978b4e852793c5e3c3efc555:
Linux 6.0-rc2 (2022-08-21 17:32:54 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-6.0-2
for you to fetch changes up to 41ac42f137080bc230b5882e3c88c392ab7f2d32:
s390/mm: do not trigger write fault when vma does not allow VM_WRITE (2022-08-25 15:12:32 +0200)
----------------------------------------------------------------
s390 updates for 6.0-rc3
- Fix double free of guarded storage and runtime instrumentation control
blocks on fork() failure.
- Fix triggering write fault when VMA does not allow VM_WRITE.
----------------------------------------------------------------
Brian Foster (1):
s390: fix double free of GS and RI CBs on fork() failure
Gerald Schaefer (1):
s390/mm: do not trigger write fault when vma does not allow VM_WRITE
arch/s390/kernel/process.c | 22 ++++++++++++++++------
arch/s390/mm/fault.c | 4 +++-
2 files changed, 19 insertions(+), 7 deletions(-)
next reply other threads:[~2022-08-27 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 10:07 Vasily Gorbik [this message]
2022-08-27 23:07 ` [GIT PULL] s390 updates for 6.0-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=your-ad-here.call-01661594879-ext-8999@work.hours \
--to=gor@linux.ibm.com \
--cc=agordeev@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