From: syzbot <syzbot+a079f084653164a652d1@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: [PATCH] WARNING in batadv_iv_ogm_process_per_outif
Date: Mon, 14 Sep 2026 18:38:47 -0700 [thread overview]
Message-ID: <6aa8a1a7.4c28b7d0.c1bba.002a.GAE@google.com> (raw)
In-Reply-To: <6aa60ec9.f81106d8.2ab401.0032.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: [PATCH] WARNING in batadv_iv_ogm_process_per_outif
Author: jchuang26@m.fudan.edu.cn
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
Reported-by: syzbot+a079f084653164a652d1@syzkaller.appspotmail.com
diff --git a/net/batman-adv/bat_iv_ogm.c b/net/batman-adv/bat_iv_ogm.c
index 53fbdbbe8..24ea350cd 100644
--- a/net/batman-adv/bat_iv_ogm.c
+++ b/net/batman-adv/bat_iv_ogm.c
@@ -1410,9 +1410,13 @@ batadv_iv_ogm_update_seqnos(const struct ethhdr *ethhdr,
return BATADV_NO_DUP;
orig_ifinfo = batadv_orig_ifinfo_new(orig_node, if_outgoing);
- if (WARN_ON(!orig_ifinfo)) {
+ if (!orig_ifinfo) {
+ /* The GFP_ATOMIC allocation inside batadv_orig_ifinfo_new()
+ * may fail under memory pressure. That is not a kernel bug,
+ * so don't WARN; just skip duplicate detection.
+ */
batadv_orig_node_put(orig_node);
- return 0;
+ return BATADV_NO_DUP;
}
spin_lock_bh(&orig_node->bat_iv.ogm_cnt_lock);
next prev parent reply other threads:[~2026-09-15 1:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 2:47 [syzbot] [batman?] WARNING in batadv_iv_ogm_process_per_outif syzbot
2026-09-13 3:21 ` Forwarded: [PATCH] batman-adv: avoid WARN_ON for orig_ifinfo allocation failure syzbot
2026-09-13 3:21 ` syzbot
2026-09-13 3:21 ` syzbot
2026-09-14 6:56 ` Forwarded: [PATCH] configfs: unhash dentry before dropping the item syzbot
2026-09-14 7:10 ` syzbot
2026-09-14 11:39 ` Forwarded: [PATCH] WARNING in batadv_iv_ogm_process_per_outif syzbot
2026-09-15 1:38 ` syzbot [this message]
2026-09-17 1:25 ` 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=6aa8a1a7.4c28b7d0.c1bba.002a.GAE@google.com \
--to=syzbot+a079f084653164a652d1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.