From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Justin Tee <justintee8345@gmail.com>,
"yi.zhang@redhat.com" <yi.zhang@redhat.com>
Cc: Chaitanya Kulkarni <ckulkarnilinux@gmail.com>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>, "hch@lst.de" <hch@lst.de>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"justin.tee@broadcom.com" <justin.tee@broadcom.com>,
"nareshgottumukkala83@gmail.com" <nareshgottumukkala83@gmail.com>,
"paul.ely@broadcom.com" <paul.ely@broadcom.com>
Subject: Re: [BUG FIX PATCH COMPILE TESTED ONLY] nvme-fc: release admin tagset if init fails
Date: Thu, 8 Jan 2026 02:10:13 +0000 [thread overview]
Message-ID: <a2feda48-515d-4e48-876a-01ea6d8d8398@nvidia.com> (raw)
In-Reply-To: <cddd1db8-3da7-44a5-bcf9-210267c30625@gmail.com>
On 1/6/26 17:37, Justin Tee wrote:
> Hi Yi,
>
> Was there a specific nvme/fc blktest case that triggered this call
> trace? Or, was this observed after stress running all nvme/fc
> blktests in a loop?
>
> Regards,
> Justin Tee
>
thanks for looking into this, it was observed when Yi reported the issue.
Irrespective of whether it is repro issue, it's still a bug ?
Can you please provide review comments ?
-ck
next prev parent reply other threads:[~2026-01-08 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-20 0:18 [BUG FIX PATCH COMPILE TESTED ONLY] nvme-fc: release admin tagset if init fails Chaitanya Kulkarni
2026-01-06 18:28 ` Chaitanya Kulkarni
2026-01-07 1:37 ` Justin Tee
2026-01-08 2:10 ` Chaitanya Kulkarni [this message]
2026-01-08 22:49 ` Justin Tee
2026-01-08 22:51 ` Justin Tee
2026-01-09 14:54 ` 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=a2feda48-515d-4e48-876a-01ea6d8d8398@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=ckulkarnilinux@gmail.com \
--cc=hch@lst.de \
--cc=justin.tee@broadcom.com \
--cc=justintee8345@gmail.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nareshgottumukkala83@gmail.com \
--cc=paul.ely@broadcom.com \
--cc=sagi@grimberg.me \
--cc=yi.zhang@redhat.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