Linux block layer
 help / color / mirror / Atom feed
From: Ye Bin <yebin10@huawei.com>
To: <josef@toxicpanda.com>, <axboe@kernel.dk>,
	<linux-block@vger.kernel.org>, <nbd@other.debian.org>
Cc: <linux-kernel@vger.kernel.org>, Ye Bin <yebin10@huawei.com>
Subject: [PATCH -next v4 0/4] Fix hungtask when nbd_config_put and sanity check for first_minor
Date: Tue, 2 Nov 2021 09:52:33 +0800	[thread overview]
Message-ID: <20211102015237.2309763-1-yebin10@huawei.com> (raw)

This patchset include two patchsets as follows:
1. Fix hungtask when nbd_config_put
https://patchwork.kernel.org/project/linux-block/list/?series=573381
2. nbd: fix sanity check for first_minor
https://lore.kernel.org/linux-block/20211021122936.758221-1-yukuai3@huawei.com/

I have consulted with Yu Kuai, and his modification has also been confirmed by him.

Ye Bin (2):
  nbd: Fix incorrect error handle when first_minor is illegal in
    nbd_dev_add
  nbd: Fix hungtask when nbd_config_put

Yu Kuai (2):
  nbd: fix max value for 'first_minor'
  nbd: fix possible overflow for 'first_minor' in nbd_dev_add()

 drivers/block/nbd.c | 42 +++++++++++++++++++-----------------------
 1 file changed, 19 insertions(+), 23 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-11-02  1:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02  1:52 Ye Bin [this message]
2021-11-02  1:52 ` [PATCH -next v4 1/4] nbd: fix max value for 'first_minor' Ye Bin
2021-11-02  1:52 ` [PATCH -next v4 2/4] nbd: fix possible overflow for 'first_minor' in nbd_dev_add() Ye Bin
2021-11-02  1:52 ` [PATCH -next v4 3/4] nbd: Fix incorrect error handle when first_minor is illegal in nbd_dev_add Ye Bin
2021-11-02  1:52 ` [PATCH -next v4 4/4] nbd: Fix hungtask when nbd_config_put Ye Bin
2021-11-02 13:04 ` [PATCH -next v4 0/4] Fix hungtask when nbd_config_put and sanity check for first_minor Josef Bacik
2021-11-02 16:50 ` 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=20211102015237.2309763-1-yebin10@huawei.com \
    --to=yebin10@huawei.com \
    --cc=axboe@kernel.dk \
    --cc=josef@toxicpanda.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbd@other.debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox