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>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [GIT PULL] s390 updates for 7.2-rc4
Date: Sun, 19 Jul 2026 01:47:45 +0200 [thread overview]
Message-ID: <ttiea3l@ub.hpns> (raw)
Hello Linus,
please pull s390 fixes for 7.2-rc4.
Thank you,
Vasily
The following changes since commit 7d5c2f679147859c1db97d9f66366ff16909abee:
s390: Add build salt to the vDSO (2026-07-08 17:02:48 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-7.2-5
for you to fetch changes up to 49145bce539117db4b6e9e83c0e5ef528e361050:
s390/perf_cpum_cf: Add missing array_index_nospec() to __hw_perf_event_init() (2026-07-15 17:35:42 +0200)
----------------------------------------------------------------
s390 updates for 7.2-rc4
- Fix checksum lib on machines without the vector facility where the
non-vector fallback made csum_partial() calculate the checksum from
address 0 instead of the provided buffer
- Fix cpum_cf perf event initialization missing speculation barrier for
user controlled event numbers used as generic event array indexes
----------------------------------------------------------------
Sumanth Korikkar (1):
s390/perf_cpum_cf: Add missing array_index_nospec() to __hw_perf_event_init()
Vasily Gorbik (1):
s390/checksum: Fix csum_partial() without vector facility
arch/s390/kernel/perf_cpum_cf.c | 3 +++
arch/s390/lib/csum-partial.c | 2 +-
2 files changed, 4 insertions(+), 1 deletion(-)
next reply other threads:[~2026-07-18 23:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 23:47 Vasily Gorbik [this message]
2026-07-19 4:17 ` [GIT PULL] s390 updates for 7.2-rc4 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=ttiea3l@ub.hpns \
--to=gor@linux.ibm.com \
--cc=agordeev@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