From: syzbot <syzbot+934ebb67352c8a490bf3@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] possible deadlock in throtl_pending_timer_fn
Date: Fri, 29 Jul 2022 22:11:08 -0700 [thread overview]
Message-ID: <00000000000061158a05e4fecb7d@google.com> (raw)
In-Reply-To: <20220730013945.1056-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+934ebb67352c8a490bf3@syzkaller.appspotmail.com
Tested on:
commit: cb71b93c Add linux-next specific files for 20220628
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=128a6b41080000
kernel config: https://syzkaller.appspot.com/x/.config?x=badbc1adb2d582eb
dashboard link: https://syzkaller.appspot.com/bug?extid=934ebb67352c8a490bf3
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=147e67aa080000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2022-07-30 5:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220730013945.1056-1-hdanton@sina.com>
2022-07-30 5:11 ` syzbot [this message]
2022-03-29 21:23 [syzbot] possible deadlock in throtl_pending_timer_fn syzbot
[not found] ` <000000000000921fd405db62096a-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2022-03-30 2:52 ` Ming Lei
2022-03-30 2:52 ` Ming Lei
2022-03-30 2:52 ` syzbot
2022-03-30 2:52 ` syzbot
[not found] ` <0000000000009518f205db66a47a-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2022-03-30 3:01 ` Ming Lei
2022-03-30 3:01 ` Ming Lei
2022-07-29 23:32 ` syzbot
2022-07-29 23:32 ` syzbot
2022-07-30 3:25 ` syzbot
2022-07-30 3:25 ` syzbot
2022-07-30 11:17 ` Ming Lei
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=00000000000061158a05e4fecb7d@google.com \
--to=syzbot+934ebb67352c8a490bf3@syzkaller.appspotmail.com \
--cc=hdanton@sina.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 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.