From: Juergen Gross <jgross@suse.com>
To: Andrey Misiurov <andrey.misyrov@gmail.com>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
Wentao Liang <vulab@iscas.ac.cn>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] xen/gntdev: fix deadlock between map ioctl and mmap
Date: Mon, 9 Nov 2026 14:59:54 +0100 [thread overview]
Message-ID: <bf23dd76-e8e5-44a7-a30d-4a5a8fd30c34@suse.com> (raw)
In-Reply-To: <20261013170745.583279-1-andrey.misyrov@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1902 bytes --]
On 13.10.26 19:07, Andrey Misiurov wrote:
> Commit 45ca1afe2fd1 ("xen/gntdev: fix error handling in ioctl") moved
> copy_to_user() in gntdev_ioctl_map_grant_ref() under priv->lock. A
> fault in copy_to_user() takes mmap_lock, while gntdev_mmap() is called
> with mmap_lock held and takes priv->lock:
>
> ioctl thread mmap thread
> mutex_lock(&priv->lock)
> mmap_write_lock(mm)
> gntdev_mmap()
> mutex_lock(&priv->lock)
> copy_to_user() faults
> mmap_read_lock(mm)
>
> Reproduced on Debian 6.12.111 in a Xen guest, with the ioctl argument
> on a MAP_PRIVATE file page that has not been written yet. sysrq-w:
>
> task:repro state:D stack:0 pid:4479 tgid:4477 ppid:1 flags:0x00000000
> rwsem_down_read_slowpath+0x25c/0x480
> down_read_killable+0x48/0xc0
> lock_mm_and_find_vma+0x96/0x250
> do_user_addr_fault+0x12d/0x620
> exc_page_fault+0x7e/0x180
> asm_exc_page_fault+0x26/0x30
> _copy_to_user+0x36/0x50
> gntdev_ioctl+0x3b9/0xa00 [xen_gntdev]
> __x64_sys_ioctl+0x97/0xc0
> task:repro state:D stack:0 pid:4480 tgid:4477 ppid:1 flags:0x00000000
> __mutex_lock.constprop.0+0x41b/0x720
> gntdev_mmap+0x4d/0x330 [xen_gntdev]
> __mmap_region+0x697/0xb10
> mmap_region+0x78/0xa0
> do_mmap+0x45d/0x630
> vm_mmap_pgoff+0xf8/0x1c0
>
> Drop priv->lock before copy_to_user() again. On failure, re-take it
> and remove the map by index, as IOCTL_GNTDEV_UNMAP_GRANT_REF does,
> since another thread may have unmapped it meanwhile.
>
> Fixes: 45ca1afe2fd1 ("xen/gntdev: fix error handling in ioctl")
> Cc: stable@vger.kernel.org
> Signed-off-by: Andrey Misiurov <andrey.misyrov@gmail.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Juergen
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2026-11-09 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 17:07 Andrey Misiurov
2026-11-09 13:59 ` 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=bf23dd76-e8e5-44a7-a30d-4a5a8fd30c34@suse.com \
--to=jgross@suse.com \
--cc=andrey.misyrov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=sstabellini@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
--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
all inboxes | Powered by JetHome®