linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Sun Ke <sunke32@huawei.com>, josef@toxicpanda.com, Markus.Elfring@web.de
Cc: linux-block@vger.kernel.org, nbd@other.debian.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/2] fix a NULL pointer bug and simplify the code
Date: Tue, 11 May 2021 07:48:24 -0600	[thread overview]
Message-ID: <6ab031d5-f836-77c9-8be0-7b3e82a087a8@kernel.dk> (raw)
In-Reply-To: <aa80f848-c895-4478-f582-10a57a1166c3@huawei.com>

On 5/11/21 12:59 AM, Sun Ke wrote:
> 
> 在 2021/2/19 9:07, Jens Axboe 写道:
>> On 2/18/21 5:26 AM, Sun Ke wrote:
>>> fix a NULL pointer bug and simplify the code
>>>
>>> v6: Just add if (nbd->recv_workq) to nbd_disconnect_and_put().
>>> v5: Adjust the title and add “Suggested-by”.
>>> v4: Share exception handling code for if branches and 
>>> 	move put_nbd adjustment to a separate patch.
>>> v3: Do not use unlock and add put_nbd.
>>> v2: Use jump target unlock.
>>>
>>> Sun Ke (2):
>>>   nbd: Fix NULL pointer in flush_workqueue
>>>   nbd: share nbd_put and return by goto put_nbd
>>>
>>>  drivers/block/nbd.c | 10 +++++-----
>>>  1 file changed, 5 insertions(+), 5 deletions(-)
>> Applied for 5.12, thanks.
> 
> Hi Jens,
> 
> I do not see the patches merged yet, is there anything wrong?

Huh, that's very strange. Not sure what happened here, care to
resend them?

-- 
Jens Axboe


      parent reply	other threads:[~2021-05-11 13:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 12:26 [PATCH v6 0/2] fix a NULL pointer bug and simplify the code Sun Ke
2021-02-18 12:26 ` [PATCH v6 1/2] nbd: Fix NULL pointer in flush_workqueue Sun Ke
2021-02-18 12:26 ` [PATCH v6 2/2] nbd: share nbd_put and return by goto put_nbd Sun Ke
2021-02-18 20:39 ` [PATCH v6 0/2] fix a NULL pointer bug and simplify the code Josef Bacik
2021-02-19  1:07 ` Jens Axboe
     [not found]   ` <aa80f848-c895-4478-f582-10a57a1166c3@huawei.com>
2021-05-11 13:48     ` 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=6ab031d5-f836-77c9-8be0-7b3e82a087a8@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Markus.Elfring@web.de \
    --cc=josef@toxicpanda.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbd@other.debian.org \
    --cc=sunke32@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;
as well as URLs for NNTP newsgroup(s).