From: Lee Jones <lee.jones@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Xie Yongji <xieyongji@bytedance.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH 1/1] virtio-blk: Use blk_validate_block_size() to validate block size
Date: Wed, 30 Mar 2022 12:07:29 +0100 [thread overview]
Message-ID: <YkQ58V4+NWgDRZ18@google.com> (raw)
In-Reply-To: <YkQ4yuX+RGPPm1hV@kroah.com>
On Wed, 30 Mar 2022, Greg KH wrote:
> On Wed, Mar 30, 2022 at 11:58:41AM +0100, Lee Jones wrote:
> > From: Xie Yongji <xieyongji@bytedance.com>
> >
> > [ Upstream commit 57a13a5b8157d9a8606490aaa1b805bafe6c37e1 ]
> >
> > The block layer can't support a block size larger than
> > page size yet. And a block size that's too small or
> > not a power of two won't work either. If a misconfigured
> > device presents an invalid block size in configuration space,
> > it will result in the kernel crash something like below:
> >
> > [ 506.154324] BUG: kernel NULL pointer dereference, address: 0000000000000008
> > [ 506.160416] RIP: 0010:create_empty_buffers+0x24/0x100
> > [ 506.174302] Call Trace:
> > [ 506.174651] create_page_buffers+0x4d/0x60
> > [ 506.175207] block_read_full_page+0x50/0x380
> > [ 506.175798] ? __mod_lruvec_page_state+0x60/0xa0
> > [ 506.176412] ? __add_to_page_cache_locked+0x1b2/0x390
> > [ 506.177085] ? blkdev_direct_IO+0x4a0/0x4a0
> > [ 506.177644] ? scan_shadow_nodes+0x30/0x30
> > [ 506.178206] ? lru_cache_add+0x42/0x60
> > [ 506.178716] do_read_cache_page+0x695/0x740
> > [ 506.179278] ? read_part_sector+0xe0/0xe0
> > [ 506.179821] read_part_sector+0x36/0xe0
> > [ 506.180337] adfspart_check_ICS+0x32/0x320
> > [ 506.180890] ? snprintf+0x45/0x70
> > [ 506.181350] ? read_part_sector+0xe0/0xe0
> > [ 506.181906] bdev_disk_changed+0x229/0x5c0
> > [ 506.182483] blkdev_get_whole+0x6d/0x90
> > [ 506.183013] blkdev_get_by_dev+0x122/0x2d0
> > [ 506.183562] device_add_disk+0x39e/0x3c0
> > [ 506.184472] virtblk_probe+0x3f8/0x79b [virtio_blk]
> > [ 506.185461] virtio_dev_probe+0x15e/0x1d0 [virtio]
> >
> > So let's use a block layer helper to validate the block size.
> >
> > Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
> > Acked-by: Michael S. Tsirkin <mst@redhat.com>
> > Link: https://lore.kernel.org/r/20211026144015.188-5-xieyongji@bytedance.com
> > Signed-off-by: Jens Axboe <axboe@kernel.dk>
> > Signed-off-by: Lee Jones <lee.jones@linaro.org>
> > ---
> > drivers/block/virtio_blk.c | 12 ++++++++++--
> > 1 file changed, 10 insertions(+), 2 deletions(-)
>
> What stable tree(s) are you wanting this backported to?
I knew there was something I'd forgotten to do.
All of them, but I will save you the work and submit separate series'.
This one is for linux-5.10.y.
--
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2022-03-30 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 10:58 [PATCH 1/1] virtio-blk: Use blk_validate_block_size() to validate block size Lee Jones
2022-03-30 11:00 ` Michael S. Tsirkin
2022-03-30 11:05 ` Lee Jones
2022-03-30 11:02 ` Greg KH
2022-03-30 11:07 ` Lee Jones [this message]
2022-03-30 11:20 ` Greg KH
2022-03-30 11:47 ` Greg KH
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=YkQ58V4+NWgDRZ18@google.com \
--to=lee.jones@linaro.org \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=mst@redhat.com \
--cc=stable@vger.kernel.org \
--cc=xieyongji@bytedance.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 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.