From: Justin Tee <justintee8345@gmail.com>
To: Shuangpeng <shuangpeng.kernel@gmail.com>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
justin.tee@broadcom.com, nareshgottumukkala83@gmail.com,
paul.ely@broadcom.com, hch@lst.de, sagi@grimberg.me,
kch@nvidia.com
Subject: Re: [BUG] KASAN: slab-use-after-free in nvmet_fc_tgt_q_put
Date: Wed, 3 Jun 2026 16:22:05 -0700 [thread overview]
Message-ID: <56c826df-efe7-4c48-9142-c32c8e3415a8@gmail.com> (raw)
In-Reply-To: <F54D7903-EA2A-4DF8-92BD-839877786139@gmail.com>
Hi Shuangpeng,
I will look into this and get back to you, but typically the nvme target
fcloop module does not indicate a real life issue when utilizing the
nvmet-fc stack on actual fibre channel hardware.
> on commit: e8c2f9fdadee7cbc75134dc463c1e0d856d6e5c7 (May 25 2026)
Was wondering what this means? Because it doesn’t look like that is an
nvme commit.
Regards,
Justin
next prev parent reply other threads:[~2026-06-03 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 3:23 Shuangpeng
2026-06-03 23:22 ` Justin Tee [this message]
2026-06-03 23:40 ` Shuangpeng
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=56c826df-efe7-4c48-9142-c32c8e3415a8@gmail.com \
--to=justintee8345@gmail.com \
--cc=hch@lst.de \
--cc=justin.tee@broadcom.com \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nareshgottumukkala83@gmail.com \
--cc=paul.ely@broadcom.com \
--cc=sagi@grimberg.me \
--cc=shuangpeng.kernel@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
all inboxes | Powered by JetHome®