Messages in this thread | | | From | zhenwei pi <> | Subject | [PATCH v4 0/1] nvmet-tcp: Fix NULL pointer dereference during release | Date | Tue, 13 Sep 2022 09:42:52 +0800 |
| |
Hi, Sagi I notice that this series "nvmet-tcp: Don't map pages which can't come from HIGHMEM" has no reply for two weeks. Is it possible to fix this critical issue firstly? Cc: Fabio M. De Francesco <fmdefrancesco@gmail.com>
v3 -> v4: - free CMD buffers only nvmet_tcp_need_data_in().
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 | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-)
-- 2.20.1
| |