From: syzbot <syzbot+a079f084653164a652d1@syzkaller.appspotmail.com>
To: jchuang26@m.fudan.edu.cn, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [batman?] WARNING in batadv_iv_ogm_process_per_outif
Date: Mon, 14 Sep 2026 00:30:02 -0700 [thread overview]
Message-ID: <6aa7a27a.a211d2ce.1a5198.028c.GAE@google.com> (raw)
In-Reply-To: <6aa79ab6.0d4cb543.1c67cf.abecSMTPIN_ADDED_BROKEN@gmr-mx.google.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+a079f084653164a652d1@syzkaller.appspotmail.com
Tested-by: syzbot+a079f084653164a652d1@syzkaller.appspotmail.com
Tested on:
commit: 50d05c7c Merge tag 'landlock-7.3-rc3' of git://git.ker..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=178e2df9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5e4e3a0e188a497e
dashboard link: https://syzkaller.appspot.com/bug?extid=a079f084653164a652d1
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: i386
patch: https://syzkaller.appspot.com/x/patch.diff?x=156c9c8e580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-09-14 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6aa79ab6.0d4cb543.1c67cf.abecSMTPIN_ADDED_BROKEN@gmr-mx.google.com>
2026-09-14 7:30 ` syzbot [this message]
[not found] <6aa7dcd7.caa6ce30.140852.4da4SMTPIN_ADDED_BROKEN@gmr-mx.google.com>
2026-09-14 16:18 ` syzbot
[not found] <6aa79dcd.717c4d5f.2255e.48efSMTPIN_ADDED_BROKEN@gmr-mx.google.com>
2026-09-14 7:39 ` syzbot
[not found] <20260913032113.14940-1-kartikey406@gmail.com>
2026-09-13 4:24 ` syzbot
[not found] <20260913032055.14922-1-kartikey406@gmail.com>
2026-09-13 4:11 ` syzbot
2026-09-13 2:47 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=6aa7a27a.a211d2ce.1a5198.028c.GAE@google.com \
--to=syzbot+a079f084653164a652d1@syzkaller.appspotmail.com \
--cc=jchuang26@m.fudan.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--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®