public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+ca3d9f693dfa69f61371@syzkaller.appspotmail.com>
To: dvyukov@google.com, gregkh@linuxfoundation.org, hdanton@sina.com,
	linux-kernel@vger.kernel.org, rafael@kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in class_register
Date: Sat, 29 Jul 2023 22:23:47 -0700	[thread overview]
Message-ID: <000000000000b19f990601ad84fd@google.com> (raw)
In-Reply-To: <00000000000055cd8405f84c5386@google.com>

This bug is marked as fixed by commit:
driver core: class : fix slab-use-after-free Read in class_register()

But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:

#syz fix: exact-commit-title

Until then the bug is still considered open and new crashes with
the same signature are ignored.

Kernel: Linux
Dashboard link: https://syzkaller.appspot.com/bug?extid=ca3d9f693dfa69f61371

---
[1] I expect the commit to be present in:

1. for-kernelci branch of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git

2. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git

3. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git

4. main branch of
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git

The full list of 9 trees can be found at
https://syzkaller.appspot.com/upstream/repos

  parent reply	other threads:[~2023-07-30  5:23 UTC|newest]

Thread overview: 7+ 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
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 [this message]
2023-08-02 14:37   ` Aleksandr Nogikh

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=000000000000b19f990601ad84fd@google.com \
    --to=syzbot+ca3d9f693dfa69f61371@syzkaller.appspotmail.com \
    --cc=dvyukov@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@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