From: Stefan Hajnoczi <stefanha@redhat.com>
To: Shigeru Yoshida <syoshida@redhat.com>
Cc: mst@redhat.com, jasowang@redhat.com, axboe@kernel.dk,
pbonzini@redhat.com, virtualization@lists.linux-foundation.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
suwan.kim027@gmail.com
Subject: Re: [PATCH v2] virtio-blk: Avoid use-after-free on suspend/resume
Date: Thu, 11 Aug 2022 13:23:37 -0400 [thread overview]
Message-ID: <YvU7GdBMNy7NbQLe@fedora> (raw)
In-Reply-To: <20220810160948.959781-1-syoshida@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2009 bytes --]
On Thu, Aug 11, 2022 at 01:09:48AM +0900, Shigeru Yoshida wrote:
> hctx->user_data is set to vq in virtblk_init_hctx(). However, vq is
> freed on suspend and reallocated on resume. So, hctx->user_data is
> invalid after resume, and it will cause use-after-free accessing which
> will result in the kernel crash something like below:
>
> [ 22.428391] Call Trace:
> [ 22.428899] <TASK>
> [ 22.429339] virtqueue_add_split+0x3eb/0x620
> [ 22.430035] ? __blk_mq_alloc_requests+0x17f/0x2d0
> [ 22.430789] ? kvm_clock_get_cycles+0x14/0x30
> [ 22.431496] virtqueue_add_sgs+0xad/0xd0
> [ 22.432108] virtblk_add_req+0xe8/0x150
> [ 22.432692] virtio_queue_rqs+0xeb/0x210
> [ 22.433330] blk_mq_flush_plug_list+0x1b8/0x280
> [ 22.434059] __blk_flush_plug+0xe1/0x140
> [ 22.434853] blk_finish_plug+0x20/0x40
> [ 22.435512] read_pages+0x20a/0x2e0
> [ 22.436063] ? folio_add_lru+0x62/0xa0
> [ 22.436652] page_cache_ra_unbounded+0x112/0x160
> [ 22.437365] filemap_get_pages+0xe1/0x5b0
> [ 22.437964] ? context_to_sid+0x70/0x100
> [ 22.438580] ? sidtab_context_to_sid+0x32/0x400
> [ 22.439979] filemap_read+0xcd/0x3d0
> [ 22.440917] xfs_file_buffered_read+0x4a/0xc0
> [ 22.441984] xfs_file_read_iter+0x65/0xd0
> [ 22.442970] __kernel_read+0x160/0x2e0
> [ 22.443921] bprm_execve+0x21b/0x640
> [ 22.444809] do_execveat_common.isra.0+0x1a8/0x220
> [ 22.446008] __x64_sys_execve+0x2d/0x40
> [ 22.446920] do_syscall_64+0x37/0x90
> [ 22.447773] entry_SYSCALL_64_after_hwframe+0x63/0xcd
>
> This patch fixes this issue by getting vq from vblk, and removes
> virtblk_init_hctx().
>
> Fixes: 4e0400525691 ("virtio-blk: support polling I/O")
> Cc: "Suwan Kim" <suwan.kim027@gmail.com>
> Signed-off-by: Shigeru Yoshida <syoshida@redhat.com>
> ---
> drivers/block/virtio_blk.c | 24 ++++++++++--------------
> 1 file changed, 10 insertions(+), 14 deletions(-)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Shigeru Yoshida <syoshida@redhat.com>
Cc: axboe@kernel.dk, mst@redhat.com, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-block@vger.kernel.org, pbonzini@redhat.com,
suwan.kim027@gmail.com
Subject: Re: [PATCH v2] virtio-blk: Avoid use-after-free on suspend/resume
Date: Thu, 11 Aug 2022 13:23:37 -0400 [thread overview]
Message-ID: <YvU7GdBMNy7NbQLe@fedora> (raw)
In-Reply-To: <20220810160948.959781-1-syoshida@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 2009 bytes --]
On Thu, Aug 11, 2022 at 01:09:48AM +0900, Shigeru Yoshida wrote:
> hctx->user_data is set to vq in virtblk_init_hctx(). However, vq is
> freed on suspend and reallocated on resume. So, hctx->user_data is
> invalid after resume, and it will cause use-after-free accessing which
> will result in the kernel crash something like below:
>
> [ 22.428391] Call Trace:
> [ 22.428899] <TASK>
> [ 22.429339] virtqueue_add_split+0x3eb/0x620
> [ 22.430035] ? __blk_mq_alloc_requests+0x17f/0x2d0
> [ 22.430789] ? kvm_clock_get_cycles+0x14/0x30
> [ 22.431496] virtqueue_add_sgs+0xad/0xd0
> [ 22.432108] virtblk_add_req+0xe8/0x150
> [ 22.432692] virtio_queue_rqs+0xeb/0x210
> [ 22.433330] blk_mq_flush_plug_list+0x1b8/0x280
> [ 22.434059] __blk_flush_plug+0xe1/0x140
> [ 22.434853] blk_finish_plug+0x20/0x40
> [ 22.435512] read_pages+0x20a/0x2e0
> [ 22.436063] ? folio_add_lru+0x62/0xa0
> [ 22.436652] page_cache_ra_unbounded+0x112/0x160
> [ 22.437365] filemap_get_pages+0xe1/0x5b0
> [ 22.437964] ? context_to_sid+0x70/0x100
> [ 22.438580] ? sidtab_context_to_sid+0x32/0x400
> [ 22.439979] filemap_read+0xcd/0x3d0
> [ 22.440917] xfs_file_buffered_read+0x4a/0xc0
> [ 22.441984] xfs_file_read_iter+0x65/0xd0
> [ 22.442970] __kernel_read+0x160/0x2e0
> [ 22.443921] bprm_execve+0x21b/0x640
> [ 22.444809] do_execveat_common.isra.0+0x1a8/0x220
> [ 22.446008] __x64_sys_execve+0x2d/0x40
> [ 22.446920] do_syscall_64+0x37/0x90
> [ 22.447773] entry_SYSCALL_64_after_hwframe+0x63/0xcd
>
> This patch fixes this issue by getting vq from vblk, and removes
> virtblk_init_hctx().
>
> Fixes: 4e0400525691 ("virtio-blk: support polling I/O")
> Cc: "Suwan Kim" <suwan.kim027@gmail.com>
> Signed-off-by: Shigeru Yoshida <syoshida@redhat.com>
> ---
> drivers/block/virtio_blk.c | 24 ++++++++++--------------
> 1 file changed, 10 insertions(+), 14 deletions(-)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-08-11 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 16:09 [PATCH v2] virtio-blk: Avoid use-after-free on suspend/resume Shigeru Yoshida
2022-08-11 12:52 ` Kim Suwan
2022-08-11 17:23 ` Stefan Hajnoczi [this message]
2022-08-11 17:23 ` Stefan Hajnoczi
2022-08-11 23:04 ` Jens Axboe
2022-08-11 23:04 ` Jens Axboe
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=YvU7GdBMNy7NbQLe@fedora \
--to=stefanha@redhat.com \
--cc=axboe@kernel.dk \
--cc=jasowang@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=suwan.kim027@gmail.com \
--cc=syoshida@redhat.com \
--cc=virtualization@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.