[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <685e9fe6.a00a0220.129264.0006.GAE@google.com>
Date: Fri, 27 Jun 2025 06:43:02 -0700
From: syzbot <syzbot+b668da2bc4cb9670bf58@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org, penguin-kernel@...ove.sakura.ne.jp,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [net?] possible deadlock in team_device_event (3)
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+b668da2bc4cb9670bf58@...kaller.appspotmail.com
Tested-by: syzbot+b668da2bc4cb9670bf58@...kaller.appspotmail.com
Tested on:
commit: 2aeda959 Add linux-next specific files for 20250627
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=114daf0c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4db16d7e2cf94450
dashboard link: https://syzkaller.appspot.com/bug?extid=b668da2bc4cb9670bf58
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
Powered by blists - more mailing lists