From: "Yu Kuai" <yukuai@fnnas.com>
To: "Zheng Qixing" <zhengqixing@huaweicloud.com>,
<josef@toxicpanda.com>, <axboe@kernel.dk>
Cc: <linux-block@vger.kernel.org>, <nbd@other.debian.org>,
<linux-kernel@vger.kernel.org>, <yi.zhang@huawei.com>,
<yangerkun@huawei.com>, <houtao1@huawei.com>,
<zhengqixing@huawei.com>
Subject: Re: [PATCH] nbd: defer config unlock in nbd_genl_connect
Date: Tue, 11 Nov 2025 22:01:05 +0800 [thread overview]
Message-ID: <49872d86-3867-41eb-916e-4debf463cc60@fnnas.com> (raw)
In-Reply-To: <20251110124920.1333561-1-zhengqixing@huaweicloud.com>
在 2025/11/10 20:49, Zheng Qixing 写道:
> There is one use-after-free warning when running NBD_CMD_CONNECT and
> NBD_CLEAR_SOCK:
>
> nbd_genl_connect
> nbd_alloc_and_init_config // config_refs=1
> nbd_start_device // config_refs=2
> set NBD_RT_HAS_CONFIG_REF open nbd // config_refs=3
> recv_work done // config_refs=2
> NBD_CLEAR_SOCK // config_refs=1
> close nbd // config_refs=0
> refcount_inc -> uaf
>
> ------------[ cut here ]------------
> refcount_t: addition on 0; use-after-free.
> WARNING: CPU: 24 PID: 1014 at lib/refcount.c:25 refcount_warn_saturate+0x12e/0x290
> nbd_genl_connect+0x16d0/0x1ab0
> genl_family_rcv_msg_doit+0x1f3/0x310
> genl_rcv_msg+0x44a/0x790
>
> The issue can be easily reproduced by adding a small delay before
> refcount_inc(&nbd->config_refs) in nbd_genl_connect():
>
> mutex_unlock(&nbd->config_lock);
> if (!ret) {
> set_bit(NBD_RT_HAS_CONFIG_REF, &config->runtime_flags);
> + printk("before sleep\n");
> + mdelay(5 * 1000);
> + printk("after sleep\n");
> refcount_inc(&nbd->config_refs);
> nbd_connect_reply(info, nbd->index);
> }
>
> Fixes: e46c7287b1c2 ("nbd: add a basic netlink interface")
> Signed-off-by: Zheng Qixing<zhengqixing@huawei.com>
> ---
> drivers/block/nbd.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
LGTM
Reviewed-by: Yu Kuai <yukuai@fnnas.com>
next prev parent reply other threads:[~2025-11-11 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 12:49 Zheng Qixing
2025-11-11 14:01 ` Yu Kuai [this message]
2025-11-11 14:55 ` 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=49872d86-3867-41eb-916e-4debf463cc60@fnnas.com \
--to=yukuai@fnnas.com \
--cc=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=zhengqixing@huawei.com \
--cc=zhengqixing@huaweicloud.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®