From: Greg KH <gregkh@linuxfoundation.org>
To: syzbot <syzbot+ca3d9f693dfa69f61371@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, rafael@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] WARNING in class_register
Date: Sun, 2 Apr 2023 10:45:32 +0200 [thread overview]
Message-ID: <2023040205-apostle-retention-cebd@gregkh> (raw)
In-Reply-To: <00000000000055cd8405f84c5386@google.com>
On Sat, Apr 01, 2023 at 01:39:42PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: a6d9e3034536 Add linux-next specific files for 20230330
> git tree: linux-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=1496edcdc80000
> kernel config: https://syzkaller.appspot.com/x/.config?x=aceb117f7924508e
> dashboard link: https://syzkaller.appspot.com/bug?extid=ca3d9f693dfa69f61371
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14f57859c80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167cc501c80000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/ec1f900ea929/disk-a6d9e303.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/fabbf89c0d22/vmlinux-a6d9e303.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/1ed05d6192fa/bzImage-a6d9e303.xz
>
> The issue was bisected to:
>
> commit dcfbb67e48a2becfce7990386e985b9c45098ee5
> Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Date: Fri Mar 24 10:01:31 2023 +0000
>
> driver core: class: use lock_class_key already present in struct subsys_private
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10190b49c80000
> final oops: https://syzkaller.appspot.com/x/report.txt?x=12190b49c80000
> console output: https://syzkaller.appspot.com/x/log.txt?x=14190b49c80000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+ca3d9f693dfa69f61371@syzkaller.appspotmail.com
> Fixes: dcfbb67e48a2 ("driver core: class: use lock_class_key already present in struct subsys_private")
Should already be fixed by:
https://lore.kernel.org/all/2023040126-blandness-duckling-bd55@gregkh/
which was a different syzbot-reported issue with this same commit.
thanks,
greg k-h
next prev parent reply other threads:[~2023-04-02 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 20:39 [syzbot] [kernel?] WARNING in class_register syzbot
2023-04-02 8:45 ` Greg KH [this message]
2023-04-03 5:22 ` Dmitry Vyukov
2023-07-02 5:22 ` [syzbot] " syzbot
2023-07-16 5:23 ` syzbot
2023-07-30 5:23 ` syzbot
2023-08-02 14:37 ` Aleksandr Nogikh
[not found] <20230401230439.284-1-hdanton@sina.com>
2023-04-02 0:39 ` [syzbot] [kernel?] " 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=2023040205-apostle-retention-cebd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=syzbot+ca3d9f693dfa69f61371@syzkaller.appspotmail.com \
--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