From: Jens Axboe <axboe@kernel.dk>
To: josef@toxicpanda.com, linan666@huaweicloud.com
Cc: linux-block@vger.kernel.org, nbd@other.debian.org,
linux-kernel@vger.kernel.org, linan122@huawei.com,
yukuai3@huawei.com, yi.zhang@huawei.com, houtao1@huawei.com,
yangerkun@huawei.com
Subject: Re: [PATCH 0/3] fix null-ptr-deref in nbd_open()
Date: Mon, 20 Nov 2023 10:16:57 -0700 [thread overview]
Message-ID: <170050061729.96172.17600082878837866184.b4-ty@kernel.dk> (raw)
In-Reply-To: <20231116162316.1740402-1-linan666@huaweicloud.com>
On Fri, 17 Nov 2023 00:23:13 +0800, linan666@huaweicloud.com wrote:
> Li Nan (3):
> nbd: fold nbd config initialization into nbd_alloc_config()
> nbd: factor out a helper to get nbd_config without holding
> 'config_lock'
> nbd: fix null-ptr-dereference while accessing 'nbd->config'
>
> drivers/block/nbd.c | 82 +++++++++++++++++++++++++++++----------------
> 1 file changed, 53 insertions(+), 29 deletions(-)
>
> [...]
Applied, thanks!
[1/3] nbd: fold nbd config initialization into nbd_alloc_config()
commit: 1b59860540a4018e8071dc18d4893ec389506b7d
[2/3] nbd: factor out a helper to get nbd_config without holding 'config_lock'
commit: 3123ac77923341774ca3ad1196ad20bb0732bf70
[3/3] nbd: fix null-ptr-dereference while accessing 'nbd->config'
commit: c2da049f419417808466c529999170f5c3ef7d3d
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-11-20 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 16:23 linan666
2023-11-16 16:23 ` [PATCH 1/3] nbd: fold nbd config initialization into nbd_alloc_config() linan666
2023-11-16 16:23 ` [PATCH 2/3] nbd: factor out a helper to get nbd_config without holding 'config_lock' linan666
2023-11-16 16:23 ` [PATCH 3/3] nbd: fix null-ptr-dereference while accessing 'nbd->config' linan666
2023-11-20 17:08 ` [PATCH 0/3] fix null-ptr-deref in nbd_open() Josef Bacik
2023-11-20 17:16 ` 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=170050061729.96172.17600082878837866184.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=houtao1@huawei.com \
--cc=josef@toxicpanda.com \
--cc=linan122@huawei.com \
--cc=linan666@huaweicloud.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 \
/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®