[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <D7OWXONOUZ1Y.19KIRCQDVRTKN@bsdbackstore.eu>
Date: Mon, 10 Feb 2025 17:40:13 +0100
From: "Maurizio Lombardi" <mlombard@...backstore.eu>
To: "Max Gurtovoy" <mgurtovoy@...dia.com>, "zhang.guanghui@...tc.cn"
<zhang.guanghui@...tc.cn>, "sagi" <sagi@...mberg.me>, "kbusch"
<kbusch@...nel.org>, "sashal" <sashal@...nel.org>, "chunguang.xu"
<chunguang.xu@...pee.com>
Cc: "linux-kernel" <linux-kernel@...r.kernel.org>, "linux-nvme"
<linux-nvme@...ts.infradead.org>, "linux-block"
<linux-block@...r.kernel.org>
Subject: Re: nvme-tcp: fix a possible UAF when failing to send request
On Mon Feb 10, 2025 at 11:24 AM CET, Max Gurtovoy wrote:
>
> It seems to me that the HOST_PATH_ERROR handling can be improved in
> nvme-tcp.
>
> In nvme-rdma we use nvme_host_path_error(rq) and nvme_cleanup_cmd(rq) in
> case we fail to submit a command..
>
> can you try to replacing nvme_tcp_end_request(blk_mq_rq_from_pdu(req),
> NVME_SC_HOST_PATH_ERROR); call with the similar logic we use in
> nvme-rdma for host path error handling ?
Yes, I could try to prepare a patch.
In any case, I think the main issue here is that nvme_tcp_poll()
should be prevented from racing against io_work... and I also think
there is a possible race condition if nvme_tcp_poll() races against
the controller resetting code.
Maurizio
Powered by blists - more mailing lists