From: Maurizio Lombardi <mlombard@redhat.com>
To: sagi@grimberg.me
Cc: zahavi.alon@gmail.com, hch@lst.de, chaitanyak@nvidia.com,
linux-nvme@lists.infradead.org, kbusch@kernel.org
Subject: [PATCH V2 0/3] Fix some kernel panics due to the host sending invalid PDUs
Date: Fri, 22 Dec 2023 16:17:47 +0100 [thread overview]
Message-ID: <20231222151750.655751-1-mlombard@redhat.com> (raw)
I used the reproducer that was published here:
https://lore.kernel.org/linux-nvme/89a927a6-2baf-434a-b1d5-50fb99beca73@grimberg.me/T/#m57f25abc944dc706125fed02cb99d86b56c5d36e
I didn't get the same call trace, however.
V2: Be sure the DATAL field is consistent with the packet size.
Add a third patch that cleans up the error code path.
Maurizio Lombardi (3):
nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU
length
nvmet-tcp: fix a crash in nvmet_req_complete()
nvmet-tcp: remove boilerplate code
drivers/nvme/target/tcp.c | 24 +++++++++++++++++-------
1 file changed, 17 insertions(+), 7 deletions(-)
--
2.39.3
next reply other threads:[~2023-12-22 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 15:17 Maurizio Lombardi [this message]
2023-12-22 15:17 ` [PATCH V2 1/3] nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length Maurizio Lombardi
2023-12-25 10:19 ` Sagi Grimberg
2023-12-22 15:17 ` [PATCH V2 2/3] nvmet-tcp: fix a crash in nvmet_req_complete() Maurizio Lombardi
2023-12-25 10:28 ` Sagi Grimberg
2023-12-29 8:51 ` Maurizio Lombardi
2024-01-01 9:44 ` Sagi Grimberg
2024-01-01 9:44 ` Sagi Grimberg
2023-12-22 15:17 ` [PATCH V2 3/3] nvmet-tcp: remove boilerplate code Maurizio Lombardi
2023-12-25 10:28 ` Sagi Grimberg
2024-01-02 21:07 ` [PATCH V2 0/3] Fix some kernel panics due to the host sending invalid PDUs Keith Busch
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=20231222151750.655751-1-mlombard@redhat.com \
--to=mlombard@redhat.com \
--cc=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=zahavi.alon@gmail.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