From: paritoshpotukuchi@gmail.com
To: linux-nvme@lists.infradead.org
Cc: justin.tee@broadcom.com, nareshgottumukkala83@gmail.com,
paul.ely@broadcom.com, hch@lst.de, sagi@grimberg.me,
kch@nvidia.com, linux-kernel@vger.kernel.org,
syzbot+df0058a8d0bdce7c4059@syzkaller.appspotmail.com,
Paritosh Potukuchi <paritosh.potukuchi@amd.com>,
Ravi Kumar <ravi.kumar3@amd.com>
Subject: [PATCH] nvmet-fc: extend critical section in nvmet_fc_remove_port()
Date: Tue, 27 Oct 2026 14:43:04 +0000 [thread overview]
Message-ID: <20261027144304.1177203-1-paritoshpotukuchi@gmail.com> (raw)
From: Paritosh Potukuchi <paritosh.potukuchi@amd.com>
Currently in nvmet_fc_remove_port the critical section starts from
the call to spin_lock_irqsave(&nvmet_fc_tgtlock, flags) and ends
before the call to nvmet_fc_portentry_unbind(pe).
nvmet_fc_portentry_unbind takes a spin_lock_irqsave on nvmet_fc_tgtlock
again, to execute its critical section. The problem here is that,
releasing the lock before calling nvmet_fc_portentry_unbind, and then
retaking the lock inside it, creates room for other threads to possibly
enter the critical section.
The solution proposed is to extend the critical section inside
nvmet_fc_remove_port, till the point where tgtport is being used.
Reported-by: syzbot+df0058a8d0bdce7c4059@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=df0058a8d0bdce7c4059
Co-developed-by: Ravi Kumar <ravi.kumar3@amd.com>
Signed-off-by: Ravi Kumar <ravi.kumar3@amd.com>
Signed-off-by: Paritosh Potukuchi <paritosh.potukuchi@amd.com>
---
drivers/nvme/target/fc.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/nvme/target/fc.c b/drivers/nvme/target/fc.c
index 1b557775e033..96d8aafb9f56 100644
--- a/drivers/nvme/target/fc.c
+++ b/drivers/nvme/target/fc.c
@@ -1271,15 +1271,11 @@ nvmet_fc_portentry_bind(struct nvmet_fc_tgtport *tgtport,
static void
nvmet_fc_portentry_unbind(struct nvmet_fc_port_entry *pe)
{
- unsigned long flags;
-
- spin_lock_irqsave(&nvmet_fc_tgtlock, flags);
if (pe->tgtport) {
nvmet_fc_tgtport_put(pe->tgtport);
pe->tgtport->pe = NULL;
}
list_del(&pe->pe_list);
- spin_unlock_irqrestore(&nvmet_fc_tgtlock, flags);
}
/*
@@ -2922,7 +2918,6 @@ nvmet_fc_remove_port(struct nvmet_port *port)
spin_lock_irqsave(&nvmet_fc_tgtlock, flags);
if (pe->tgtport && nvmet_fc_tgtport_get(pe->tgtport))
tgtport = pe->tgtport;
- spin_unlock_irqrestore(&nvmet_fc_tgtlock, flags);
nvmet_fc_portentry_unbind(pe);
@@ -2932,6 +2927,8 @@ nvmet_fc_remove_port(struct nvmet_port *port)
nvmet_fc_tgtport_put(tgtport);
}
+ spin_unlock_irqrestore(&nvmet_fc_tgtlock, flags);
+
kfree(pe);
}
--
2.55.0
next reply other threads:[~2026-10-27 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 14:43 paritoshpotukuchi [this message]
2026-10-27 14:58 ` Maurizio Lombardi
2026-10-27 15:54 ` paritoshpotukuchi
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=20261027144304.1177203-1-paritoshpotukuchi@gmail.com \
--to=paritoshpotukuchi@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=paritosh.potukuchi@amd.com \
--cc=paul.ely@broadcom.com \
--cc=ravi.kumar3@amd.com \
--cc=sagi@grimberg.me \
--cc=syzbot+df0058a8d0bdce7c4059@syzkaller.appspotmail.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®