From: Sagi Grimberg <sagi@grimberg.me>
To: zhenwei pi <pizhenwei@bytedance.com>, hch@lst.de
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND for nvme-6.1] nvmet-tcp: Fix NULL pointer dereference during release
Date: Wed, 21 Sep 2022 11:20:40 +0300 [thread overview]
Message-ID: <cc1729fb-0a4e-b9f7-caf2-26716629aa2d@grimberg.me> (raw)
In-Reply-To: <ecdacc31-0e9f-2dc8-297a-477d24e4f581@bytedance.com>
> Hi, Sagi
>
> What about letting this patch fix the kernel panic only, and I'll send a
> followup patch to remove nvmet_tcp_finish_cmd after this patch applies?
That is fine with me.
>
>> Other than that,
>> Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
prev parent reply other threads:[~2022-09-21 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 13:16 zhenwei pi
2022-09-20 15:34 ` Sagi Grimberg
2022-09-21 2:50 ` zhenwei pi
2022-09-21 8:20 ` Sagi Grimberg [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=cc1729fb-0a4e-b9f7-caf2-26716629aa2d@grimberg.me \
--to=sagi@grimberg.me \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=pizhenwei@bytedance.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®