From: syzbot <syzbot+b668da2bc4cb9670bf58@syzkaller.appspotmail.com>
To: aha310510@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] possible deadlock in team_device_event (3)
Date: Thu, 01 Aug 2024 03:22:03 -0700 [thread overview]
Message-ID: <000000000000f4fdee061e9c94ab@google.com> (raw)
In-Reply-To: <20240801095632.49339-1-aha310510@gmail.com>
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: 21b136cc minmax: fix up min3() and max3() too
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1194416d980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7c04fc17f2c61c03
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
patch: https://syzkaller.appspot.com/x/patch.diff?x=172317a1980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-08-01 10:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240801095632.49339-1-aha310510@gmail.com>
2024-08-01 10:22 ` syzbot [this message]
[not found] <20240802141947.89103-1-aha310510@gmail.com>
2024-08-02 14:46 ` [syzbot] [net?] possible deadlock in team_device_event (3) syzbot
[not found] <20240731141548.13707-1-aha310510@gmail.com>
2024-07-31 14:44 ` syzbot
[not found] <20240731131908.13019-1-aha310510@gmail.com>
2024-07-31 13:39 ` syzbot
[not found] <20240731121721.9000-1-aha310510@gmail.com>
2024-07-31 12:40 ` syzbot
[not found] <20240730124026.24187-1-aha310510@gmail.com>
2024-07-30 13:07 ` syzbot
[not found] <20240730120121.23576-1-aha310510@gmail.com>
2024-07-30 12:25 ` syzbot
[not found] <20240730112225.20076-1-aha310510@gmail.com>
2024-07-30 11:45 ` syzbot
2024-05-09 16:54 syzbot
2024-07-26 18:36 ` syzbot
2025-06-27 13:23 ` Tetsuo Handa
2025-06-27 13:43 ` syzbot
2025-06-27 13:47 ` Tetsuo Handa
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=000000000000f4fdee061e9c94ab@google.com \
--to=syzbot+b668da2bc4cb9670bf58@syzkaller.appspotmail.com \
--cc=aha310510@gmail.com \
--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