From: syzbot <syzbot+b668da2bc4cb9670bf58@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] possible deadlock in team_device_event (3)
Date: Fri, 27 Jun 2025 06:43:02 -0700 [thread overview]
Message-ID: <685e9fe6.a00a0220.129264.0006.GAE@google.com> (raw)
In-Reply-To: <d1312fe5-a38b-4522-8330-998410da7980@I-love.SAKURA.ne.jp>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+b668da2bc4cb9670bf58@syzkaller.appspotmail.com
Tested-by: syzbot+b668da2bc4cb9670bf58@syzkaller.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.
next prev parent reply other threads:[~2025-06-27 13:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 16:54 [syzbot] [net?] possible deadlock in team_device_event (3) syzbot
2024-07-26 18:36 ` syzbot
2024-07-30 11:23 ` [syzbot] " syzbot
2024-07-30 12:02 ` syzbot
2024-07-30 12:41 ` syzbot
2024-07-31 12:18 ` syzbot
2024-07-31 13:20 ` syzbot
2024-07-31 14:16 ` syzbot
2024-08-01 9:57 ` syzbot
2024-08-02 14:20 ` syzbot
2025-06-27 13:23 ` Tetsuo Handa
2025-06-27 13:43 ` syzbot [this message]
2025-06-27 13:47 ` Tetsuo Handa
[not found] <20240730112225.20076-1-aha310510@gmail.com>
2024-07-30 11:45 ` syzbot
[not found] <20240730120121.23576-1-aha310510@gmail.com>
2024-07-30 12:25 ` syzbot
[not found] <20240730124026.24187-1-aha310510@gmail.com>
2024-07-30 13:07 ` syzbot
[not found] <20240731121721.9000-1-aha310510@gmail.com>
2024-07-31 12:40 ` syzbot
[not found] <20240731131908.13019-1-aha310510@gmail.com>
2024-07-31 13:39 ` syzbot
[not found] <20240731141548.13707-1-aha310510@gmail.com>
2024-07-31 14:44 ` syzbot
[not found] <20240801095632.49339-1-aha310510@gmail.com>
2024-08-01 10:22 ` syzbot
[not found] <20240802141947.89103-1-aha310510@gmail.com>
2024-08-02 14:46 ` 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=685e9fe6.a00a0220.129264.0006.GAE@google.com \
--to=syzbot+b668da2bc4cb9670bf58@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--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.