From: zhenwei pi <pizhenwei@bytedance.com>
To: hch@lst.de, sagi@grimberg.me
Cc: kch@nvidia.com, linux-nvme@lists.infradead.org,
linux-kernel@vger.kernel.org,
zhenwei pi <pizhenwei@bytedance.com>
Subject: [PATCH v3 0/1] nvmet-tcp: Fix NULL pointer dereference during release
Date: Thu, 1 Sep 2022 14:14:08 +0800 [thread overview]
Message-ID: <20220901061409.545456-1-pizhenwei@bytedance.com> (raw)
v2 -> v3:
- Keep original function name as nvmet_tcp_uninit_data_in_cmds()
- Add new function nvmet_tcp_free_cmd_data_in_buffers() to free CMD buffers
- Rework against http://git.infradead.org/nvme.git/shortlog/refs/heads/nvme-6.0
- Move nvmet_tcp_free_cmd_data_in_buffers() after cancel_work_sync(&queue->io_work).
Hi @Sagi, if you still prefer to clear the commands that are still waiting for
data from the wire, please let me know.
v1 -> v2:
- Separate nvmet_tcp_uninit_data_in_cmds() into nvmet_tcp_uninit_req()
& nvmet_tcp_uninit_data_in_cmds()(free buffers only).
v1:
- Move nvmet_tcp_uninit_data_in_cmds() after nvmet_sq_destroy()
zhenwei pi (1):
nvmet-tcp: Fix NULL pointer dereference during release
drivers/nvme/target/tcp.c | 18 ++++++++++++++++--
1 file changed, 16 insertions(+), 2 deletions(-)
--
2.20.1
next reply other threads:[~2022-09-01 6:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 6:14 zhenwei pi [this message]
2022-09-01 6:14 ` [PATCH v3 1/1] " zhenwei pi
2022-09-01 10:52 ` Sagi Grimberg
2022-09-02 2:37 ` zhenwei pi
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=20220901061409.545456-1-pizhenwei@bytedance.com \
--to=pizhenwei@bytedance.com \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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®