mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Steffen Eiden <seiden@linux.ibm.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: David Hildenbrand <david@kernel.org>,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	Christoph Schlameuss <schlameuss@linux.ibm.com>,
	Harald Freudenberger <freude@linux.ibm.com>,
	kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] s390/uv: Various fixes for UV secrets
Date: Wed, 19 Aug 2026 09:18:32 +0200	[thread overview]
Message-ID: <5bb2ece6-acef-4348-a08b-5adfab758b1b@linux.ibm.com> (raw)
In-Reply-To: <20260812-uv_secrets_fix-v3-0-a85bd29e0666@linux.ibm.com>

Am 12.08.26 um 17:55 schrieb Steffen Eiden:
> To: Christian Borntraeger <borntraeger@linux.ibm.com>
> To: Janosch Frank <frankja@linux.ibm.com>
> To: Claudio Imbrenda <imbrenda@linux.ibm.com>
> Cc: David Hildenbrand <david@kernel.org>
> Cc: Heiko Carstens <hca@linux.ibm.com>
> Cc: Vasily Gorbik <gor@linux.ibm.com>
> Cc: Alexander Gordeev <agordeev@linux.ibm.com>
> Cc: Sven Schnelle <svens@linux.ibm.com>
> Cc: Christoph Schlameuss <schlameuss@linux.ibm.com>
> Cc: Harald Freudenberger <freude@linux.ibm.com>
> Cc: Steffen Eiden <seiden@linux.ibm.com>
> Cc: kvm@vger.kernel.org
> Cc: linux-s390@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> 
> Fix some issues in the retrieve secret infrastructure. First, fix the
> issue that the loop in uv_find_secret cannot ran more that one round.
> Second, fix a potential out of bounds issue in find_secret_in_page.
> 
> ---
> Changes in v3:
> - Add R-b from Christoph for patch 1
> - Improved commit message in patch 1
> - Link to v2: https://lore.kernel.org/r/20260811-uv_secrets_fix-v2-0-64444968ec55@linux.ibm.com
> Changes in v2:
> - Add Ack from Claudio
> - Add patch that fixes a potential out-of-bounds access in find_secret_in_page
> - Link to v1: https://lore.kernel.org/r/20260811-uv_secrets_fix-v1-1-940a421a9292@linux.ibm.com
> 
> ---
> Steffen Eiden (2):
>        s390/uv: Fix loop condition in uv_find_secrets
>        s390/uv: Prevent potential out-of-bounds read
> 
>   arch/s390/kernel/uv.c | 8 +++++---
>   1 file changed, 5 insertions(+), 3 deletions(-)
> ---
> base-commit: d58772d8520c7ef247c4b95c9bd76d3a25da9ff5
> change-id: 20260811-uv_secrets_fix-58a63b4a4ec4
> 
> Best regards,


Thanks applied.

      parent reply	other threads:[~2026-08-19  7:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12 15:55 Steffen Eiden
2026-08-12 15:55 ` [PATCH v3 1/2] s390/uv: Fix loop condition in uv_find_secrets Steffen Eiden
2026-08-12 15:55 ` [PATCH v3 2/2] s390/uv: Prevent potential out-of-bounds read Steffen Eiden
2026-08-13 10:20   ` Christoph Schlameuss
2026-08-19  7:18 ` Christian Borntraeger [this message]

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=5bb2ece6-acef-4348-a08b-5adfab758b1b@linux.ibm.com \
    --to=borntraeger@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=david@kernel.org \
    --cc=frankja@linux.ibm.com \
    --cc=freude@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=schlameuss@linux.ibm.com \
    --cc=seiden@linux.ibm.com \
    --cc=svens@linux.ibm.com \
    /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®