From: syzbot <syzbot+4bd730aede2791e40bdf@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: [PATCH] WARNING: suspicious RCU usage in expect_iter_name
Date: Mon, 14 Sep 2026 18:38:40 -0700 [thread overview]
Message-ID: <6aa8a1a0.a211d2ce.1a5198.02a0.GAE@google.com> (raw)
In-Reply-To: <6aa4a377.f81106d8.2ab401.0024.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: [PATCH] WARNING: suspicious RCU usage in expect_iter_name
Author: jchuang26@m.fudan.edu.cn
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git master
Reported-by: syzbot+4bd730aede2791e40bdf@syzkaller.appspotmail.com
diff --git a/net/netfilter/nf_conntrack_netlink.c b/net/netfilter/nf_conntrack_netlink.c
index 9b4e29557..2449df2e9 100644
--- a/net/netfilter/nf_conntrack_netlink.c
+++ b/net/netfilter/nf_conntrack_netlink.c
@@ -3390,7 +3390,13 @@ static bool expect_iter_name(struct nf_conntrack_expect *exp, void *data)
struct nf_conntrack_helper *helper;
const char *name = data;
- helper = rcu_dereference(exp->helper);
+ /* This iterator runs under nf_conntrack_expect_lock (see
+ * nf_ct_expect_iterate_net()), which serializes changes to exp->helper.
+ * Use the protected accessor to document that lock-based protection and
+ * avoid a bogus RCU lockdep splat.
+ */
+ helper = rcu_dereference_protected(exp->helper,
+ lockdep_is_held(&nf_conntrack_expect_lock));
if (!helper)
return false;
prev parent reply other threads:[~2026-09-15 1:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 0:57 [syzbot] [netfilter?] " syzbot
2026-09-14 11:53 ` Forwarded: [PATCH] " syzbot
2026-09-15 1:38 ` syzbot [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=6aa8a1a0.a211d2ce.1a5198.02a0.GAE@google.com \
--to=syzbot+4bd730aede2791e40bdf@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®