public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Matthew Rosato <mjrosato@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, freimuth@linux.ibm.com,
	imbrenda@linux.ibm.com, borntraeger@linux.ibm.com
Subject: Re: [PATCH v2 1/2] KVM: s390: Limit adapter indicator access to mapped page
Date: Mon, 9 Mar 2026 13:17:30 +0100	[thread overview]
Message-ID: <67b67097-c4d5-470f-9653-8cb30cddd3f7@linux.ibm.com> (raw)
In-Reply-To: <9eef692a-7d8f-4082-89e0-22210c407395@linux.ibm.com>

On 3/5/26 15:04, Matthew Rosato wrote:
> On 3/4/26 3:16 PM, Matthew Rosato wrote:
>> On 3/3/26 8:46 AM, Janosch Frank wrote:
>>> While we check the address for errors, we don't seem to check the bit
>>> offsets and since they are 32 and 64 bits a lot of memory can be
>>> reached indirectly via those offsets.
>>>
>>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>>> Fixes: 84223598778b ("KVM: s390: irq routing for adapter interrupts.")
>>> Suggested-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
>>
>> Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
>>
> 
> Like with v1, I used a modified QEMU to attempt various invocations to convince myself this works.  So feel free to also add:
> 
> Tested-by: Matthew Rosato <mjrosato@linux.ibm.com>
> 
> 
> 

Thank you for testing this!

  reply	other threads:[~2026-03-09 12:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-03 13:46 [PATCH v2 0/2] KVM: s390: Limit adapter indicator access to page Janosch Frank
2026-03-03 13:46 ` [PATCH v2 1/2] KVM: s390: Limit adapter indicator access to mapped page Janosch Frank
2026-03-04 20:16   ` Matthew Rosato
2026-03-05 14:04     ` Matthew Rosato
2026-03-09 12:17       ` Janosch Frank [this message]
2026-03-05 16:52   ` Christian Borntraeger
2026-03-03 13:46 ` [PATCH v2 2/2] KVM: s390: selftests: Add IRQ routing address offset tests Janosch Frank
2026-03-04 20:19   ` Matthew Rosato
2026-03-05 14:27     ` Matthew Rosato

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=67b67097-c4d5-470f-9653-8cb30cddd3f7@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=freimuth@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mjrosato@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