From: Juergen Gross <jgross@suse.com>
To: Val Packett <val@invisiblethingslab.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Cc: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux.dev
Subject: Re: [PATCH] xen: privcmd: fix ioeventfd crash under PV domain
Date: Mon, 3 Aug 2026 16:11:07 +0200 [thread overview]
Message-ID: <8b5d403c-e77a-45cb-9e3c-d6ccc8ea7a20@suse.com> (raw)
In-Reply-To: <20260708082934.16038-1-val@invisiblethingslab.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 585 bytes --]
On 08.07.26 10:18, Val Packett wrote:
> Starting a virtio backend in a PV domain would panic the kernel in
> alloc_ioreq, trying to dereference vma->vm_private_data as a pages
> pointer when in reality it stayed as PRIV_VMA_LOCKED.
>
> Avoid crashing by handling the PRIV_VMA_LOCKED case in alloc_ioreq.
> PV support requires mapping the virtio ioreq page explicitly into
> the kernel's page tables, so do it on-demand when PRIV_VMA_LOCKED
> is seen.
>
> Signed-off-by: Val Packett <val@invisiblethingslab.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2026-08-03 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 8:18 [PATCH] xen: privcmd: fix ioeventfd crash under PV domain Val Packett
2026-08-03 14:11 ` Juergen Gross [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=8b5d403c-e77a-45cb-9e3c-d6ccc8ea7a20@suse.com \
--to=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=sstabellini@kernel.org \
--cc=val@invisiblethingslab.com \
--cc=virtualization@lists.linux.dev \
--cc=xen-devel@lists.xenproject.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