mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+c98b21427617af7f547a@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nvme?] BUG: corrupted list in nvmet_fc_remove_port
Date: Mon, 12 Oct 2026 20:41:56 +0800	[thread overview]
Message-ID: <20261012124158.498-1-hdanton@sina.com> (raw)
In-Reply-To: <6acbc835.a150a118.27e199.003c.GAE@google.com>

> Date: Sun, 11 Oct 2026 10:32:37 -0700	[thread overview]
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    a5ebb76233b7 Merge tag 'edac_urgent_for_v7.3_rc7' of git:/..
> git tree:       upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=1494923e580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=df4bbab1c2172b9f
> dashboard link: https://syzkaller.appspot.com/bug?extid=c98b21427617af7f547a
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=126a0f15580000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=166a0f15580000

#syz test

--- x/drivers/nvme/target/fc.c
+++ y/drivers/nvme/target/fc.c
@@ -1620,6 +1620,7 @@ nvmet_fc_free_pending_reqs(struct nvmet_
 	}
 }
 
+static DEFINE_MUTEX(tgtp_mutex);
 /**
  * nvmet_fc_unregister_targetport - transport entry point called by an
  *                              LLDD to deregister/remove a previously
@@ -1637,6 +1638,7 @@ nvmet_fc_unregister_targetport(struct nv
 	struct nvmet_fc_tgtport *tgtport = targetport_to_tgtport(target_port);
 	unsigned long flags;
 
+	mutex_lock(&tgtp_mutex);
 	spin_lock_irqsave(&nvmet_fc_tgtlock, flags);
 	list_del(&tgtport->tgt_list);
 	spin_unlock_irqrestore(&nvmet_fc_tgtlock, flags);
@@ -1645,6 +1647,7 @@ nvmet_fc_unregister_targetport(struct nv
 
 	/* terminate any outstanding associations */
 	__nvmet_fc_free_assocs(tgtport);
+	mutex_unlock(&tgtp_mutex);
 
 	flush_workqueue(nvmet_wq);
 
@@ -2919,6 +2922,7 @@ nvmet_fc_remove_port(struct nvmet_port *
 	struct nvmet_fc_tgtport *tgtport = NULL;
 	unsigned long flags;
 
+	mutex_lock(&tgtp_mutex);
 	spin_lock_irqsave(&nvmet_fc_tgtlock, flags);
 	if (pe->tgtport && nvmet_fc_tgtport_get(pe->tgtport))
 		tgtport = pe->tgtport;
@@ -2933,6 +2937,7 @@ nvmet_fc_remove_port(struct nvmet_port *
 	}
 
 	kfree(pe);
+	mutex_unlock(&tgtp_mutex);
 }
 
 static void
--

  parent reply	other threads:[~2026-10-12 12:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-11 17:32 syzbot
2026-10-12  5:11 ` Hillf Danton
2026-10-12  5:50   ` syzbot
2026-10-12  7:58 ` Hillf Danton
2026-10-12  8:25   ` syzbot
2026-10-12 10:33 ` Hillf Danton
2026-10-12 11:01   ` syzbot
2026-10-12 12:41 ` Hillf Danton [this message]
2026-10-12 13:11   ` syzbot

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=20261012124158.498-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+c98b21427617af7f547a@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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®