From: syzbot <syzbot+17bc8c5157022e18da8b@syzkaller.appspotmail.com>
To: apparmor-owner@lists.ubuntu.com, apparmor@lists.ubuntu.com,
edumazet@google.com, jmorris@namei.org,
john.johansen@canonical.com, john@apparmor.net, kuba@kernel.org,
kuniyu@amazon.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
paul@paul-moore.com, penguin-kernel@i-love.sakura.ne.jp,
razor@blackwall.org, serge@hallyn.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net] INFO: rcu detected stall in sys_getdents64
Date: Sat, 22 Mar 2025 23:53:03 -0700 [thread overview]
Message-ID: <67dfafcf.050a0220.31a16b.0058.GAE@google.com> (raw)
In-Reply-To: <6707499c.050a0220.1139e6.0017.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit e759e1e4a4bd2926d082afe56046a90224433a31
Author: Eric Dumazet <edumazet@google.com>
Date: Wed Jan 29 14:27:26 2025 +0000
net: revert RTNL changes in unregister_netdevice_many_notify()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1084f004580000
start commit: fc20a3e57247 Merge tag 'for-linus-6.12a-rc2-tag' of git://..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ba92623fdea824c9
dashboard link: https://syzkaller.appspot.com/bug?extid=17bc8c5157022e18da8b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=135f7d27980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1483b380580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net: revert RTNL changes in unregister_netdevice_many_notify()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-03-23 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 3:27 [syzbot] [apparmor?] [ext4?] INFO: rcu detected stall in sys_getdents64 syzbot
2024-10-10 9:48 ` Tetsuo Handa
2024-10-10 10:00 ` Nikolay Aleksandrov
2024-10-10 10:34 ` Tetsuo Handa
2025-03-23 6:53 ` 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=67dfafcf.050a0220.31a16b.0058.GAE@google.com \
--to=syzbot+17bc8c5157022e18da8b@syzkaller.appspotmail.com \
--cc=apparmor-owner@lists.ubuntu.com \
--cc=apparmor@lists.ubuntu.com \
--cc=edumazet@google.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=john@apparmor.net \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=razor@blackwall.org \
--cc=serge@hallyn.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 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.