From: Nikolay Aleksandrov <razor@blackwall.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
syzbot <syzbot+17bc8c5157022e18da8b@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Network Development <netdev@vger.kernel.org>
Subject: Re: [syzbot] [apparmor?] [ext4?] INFO: rcu detected stall in sys_getdents64
Date: Thu, 10 Oct 2024 13:00:45 +0300 [thread overview]
Message-ID: <879c5998-cd65-473d-962a-7f4442979ab4@blackwall.org> (raw)
In-Reply-To: <7fbdb7db-57c3-47b8-89ed-da974d03f17f@I-love.SAKURA.ne.jp>
On 10/10/2024 12:48, Tetsuo Handa wrote:
> This is a printk() flooding problem in bridge driver. Should consider using ratelimit.
>
> #syz set subsystems: net
>
It should already be ratelimited, the code that prints is:
if (net_ratelimit())
br_warn(br, "received packet on %s with own address as source address (addr:%pM, vlan:%u)\n",
source->dev->name, addr, vid);
Cheers,
Nik
> On 2024/10/10 12:27, syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: fc20a3e57247 Merge tag 'for-linus-6.12a-rc2-tag' of git://..
>> git tree: upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=1083b380580000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=ba92623fdea824c9
>> dashboard link: https://syzkaller.appspot.com/bug?extid=17bc8c5157022e18da8b
>> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=135f7d27980000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1483b380580000
>>
>> Downloadable assets:
>> disk image: https://storage.googleapis.com/syzbot-assets/2ad9af7b84b4/disk-fc20a3e5.raw.xz
>> vmlinux: https://storage.googleapis.com/syzbot-assets/1afa462ca485/vmlinux-fc20a3e5.xz
>> kernel image: https://storage.googleapis.com/syzbot-assets/75c0900b4786/bzImage-fc20a3e5.xz
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> Reported-by: syzbot+17bc8c5157022e18da8b@syzkaller.appspotmail.com
>>
>> bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
>> rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
>> rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P5244/1:b..l
>> rcu: (detected by 1, t=10503 jiffies, g=5253, q=1466 ncpus=2)
>> task:syz-executor116 state:R running task stack:18800 pid:5244 tgid:5244 ppid:5243 flags:0x00000002
> (...snipped...)
>> net_ratelimit: 33488 callbacks suppressed
>> bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
>> bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
>> bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
>> bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
>> bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
>> bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
>> bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
>> bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
>> bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
>> bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
>
>
next prev parent reply other threads:[~2024-10-10 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 3:27 syzbot
2024-10-10 9:48 ` Tetsuo Handa
2024-10-10 10:00 ` Nikolay Aleksandrov [this message]
2024-10-10 10:34 ` Tetsuo Handa
2025-03-23 6:53 ` [syzbot] [net] " 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=879c5998-cd65-473d-962a-7f4442979ab4@blackwall.org \
--to=razor@blackwall.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=syzbot+17bc8c5157022e18da8b@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®