From: Jens Axboe <axboe@kernel.dk>
To: josef@toxicpanda.com, Zhong Jinghua <zhongjinghua@huawei.com>
Cc: linux-block@vger.kernel.org, nbd@other.debian.org,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
yukuai3@huawei.com, houtao1@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH-next] nbd: fix incomplete validation of ioctl arg
Date: Thu, 20 Apr 2023 16:10:18 -0600 [thread overview]
Message-ID: <168202861821.155232.3879480866523352390.b4-ty@kernel.dk> (raw)
In-Reply-To: <20230206145805.2645671-1-zhongjinghua@huawei.com>
On Mon, 06 Feb 2023 22:58:05 +0800, Zhong Jinghua wrote:
> We tested and found an alarm caused by nbd_ioctl arg without verification.
> The UBSAN warning calltrace like below:
>
> UBSAN: Undefined behaviour in fs/buffer.c:1709:35
> signed integer overflow:
> -9223372036854775808 - 1 cannot be represented in type 'long long int'
> CPU: 3 PID: 2523 Comm: syz-executor.0 Not tainted 4.19.90 #1
> Hardware name: linux,dummy-virt (DT)
> Call trace:
> dump_backtrace+0x0/0x3f0 arch/arm64/kernel/time.c:78
> show_stack+0x28/0x38 arch/arm64/kernel/traps.c:158
> __dump_stack lib/dump_stack.c:77 [inline]
> dump_stack+0x170/0x1dc lib/dump_stack.c:118
> ubsan_epilogue+0x18/0xb4 lib/ubsan.c:161
> handle_overflow+0x188/0x1dc lib/ubsan.c:192
> __ubsan_handle_sub_overflow+0x34/0x44 lib/ubsan.c:206
> __block_write_full_page+0x94c/0xa20 fs/buffer.c:1709
> block_write_full_page+0x1f0/0x280 fs/buffer.c:2934
> blkdev_writepage+0x34/0x40 fs/block_dev.c:607
> __writepage+0x68/0xe8 mm/page-writeback.c:2305
> write_cache_pages+0x44c/0xc70 mm/page-writeback.c:2240
> generic_writepages+0xdc/0x148 mm/page-writeback.c:2329
> blkdev_writepages+0x2c/0x38 fs/block_dev.c:2114
> do_writepages+0xd4/0x250 mm/page-writeback.c:2344
>
> [...]
Applied, thanks!
[1/1] nbd: fix incomplete validation of ioctl arg
commit: 55793ea54d77719a071b1ccc05a05056e3b5e009
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-04-20 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 14:58 Zhong Jinghua
2023-03-01 3:48 ` zhongjinghua
2023-03-14 7:10 ` zhongjinghua
2023-03-14 7:11 ` zhongjinghua
2023-04-20 12:47 ` Yu Kuai
2023-04-20 19:41 ` Josef Bacik
2023-04-20 22:10 ` Jens Axboe [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=168202861821.155232.3879480866523352390.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=houtao1@huawei.com \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@other.debian.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.com \
--cc=zhongjinghua@huawei.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
all inboxes | Powered by JetHome®