From: syzbot <syzbot+dd3c97de244683533381@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] general protection fault in __device_attach
Date: Fri, 03 Jun 2022 03:41:08 -0700 [thread overview]
Message-ID: <0000000000009ecba705e088c2ee@google.com> (raw)
In-Reply-To: <20220603074439.5255-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+dd3c97de244683533381@syzkaller.appspotmail.com
Tested on:
commit: d1dc8776 assoc_array: Fix BUG_ON during garbage collect
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=c51cd24814bb5665
dashboard link: https://syzkaller.appspot.com/bug?extid=dd3c97de244683533381
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=1244e933f00000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2022-06-03 10:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220603074439.5255-1-hdanton@sina.com>
2022-06-03 10:41 ` syzbot [this message]
[not found] <20220603033532.5154-1-hdanton@sina.com>
2022-06-03 3:55 ` [syzbot] general protection fault in __device_attach syzbot
2022-03-14 8:46 syzbot
2022-06-02 19:49 ` syzbot
2022-06-03 10:02 ` syzbot
2022-06-03 11:04 ` Andy Shevchenko
2022-06-03 15:42 ` Alan Stern
2022-06-03 15:52 ` Greg KH
2022-06-03 16:03 ` Alan Stern
2022-06-03 16:11 ` Greg KH
2022-06-03 16:27 ` Alan Stern
2022-06-04 8:32 ` Dmitry Vyukov
2022-06-06 12:38 ` Dan Carpenter
2022-06-07 7:15 ` Dmitry Vyukov
2022-06-08 3:25 ` Matthew Wilcox
2022-06-08 8:20 ` Dmitry Vyukov
2022-06-08 8:24 ` Dmitry Vyukov
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=0000000000009ecba705e088c2ee@google.com \
--to=syzbot+dd3c97de244683533381@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.