From: James Smart <jsmart2021@gmail.com>
To: duoming@zju.edu.cn
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
james.smart@broadcom.com, kbusch@kernel.org, axboe@fb.com,
hch@lst.de, sagi@grimberg.me
Subject: Re: [PATCH] nvme-fc: fix sleep-in-atomic-context bug caused by nvme_fc_rcv_ls_req
Date: Tue, 4 Oct 2022 06:51:54 -0700 [thread overview]
Message-ID: <7bebb1cc-211a-dac4-3daa-ce005156f2f9@gmail.com> (raw)
In-Reply-To: <118cdb2e.1067d5.183a2b07fa7.Coremail.duoming@zju.edu.cn>
On 10/4/2022 4:10 AM, duoming@zju.edu.cn wrote:
>> looking further... lpfc_poll_timeout() should only be used on an SLI-3
>> adapter. The existing SLI-3 adapters don't support NVMe. So I'm a
>> little confused by this stack trace.
> I found this problem through a static analysis tool wroten by myself.
> I think the hacker may simulate the hardware to trigger this stack trace.
> So, I send the patch to correct the problem.
>
>> Can you describe what the system config/software setup is and
>> specifically what lpfc adapter is being used (dmesg attachment logs are
>> sufficient, or lspci output).
> Best regards,
> Duoming Zhou
>
ok - so the patch is to the tool ? as the code path doesn't actually occur ?
-- james
prev parent reply other threads:[~2022-10-04 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 0:19 [PATCH] nvme-fc: fix sleep-in-atomic-context bug caused by nvme_fc_rcv_ls_req Duoming Zhou
2022-10-02 17:12 ` James Smart
2022-10-03 1:50 ` duoming
2022-10-03 2:56 ` James Smart
2022-10-03 17:48 ` James Smart
2022-10-04 11:10 ` duoming
2022-10-04 13:51 ` James Smart [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=7bebb1cc-211a-dac4-3daa-ce005156f2f9@gmail.com \
--to=jsmart2021@gmail.com \
--cc=axboe@fb.com \
--cc=duoming@zju.edu.cn \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=kbusch@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).