public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7f4f9a43a9c78eaee04f@syzkaller.appspotmail.com>
To: Jason@zx2c4.com, bigeasy@linutronix.de, boqun.feng@gmail.com,
	 hdanton@sina.com, jason@zx2c4.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] WARNING: locking bug in get_random_u8
Date: Mon, 24 Feb 2025 06:51:16 -0800	[thread overview]
Message-ID: <67bc8764.050a0220.bbfd1.0088.GAE@google.com> (raw)
In-Reply-To: <6738c3ba.050a0220.bb738.000d.GAE@google.com>

This bug is marked as fixed by commit:
kasan: Make kasan_record_aux_stack_noalloc() the default behaviour

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=7f4f9a43a9c78eaee04f

---
[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 10 trees can be found at
https://syzkaller.appspot.com/upstream/repos

  parent reply	other threads:[~2025-02-24 14:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-16 16:09 [syzbot] [kernel?] WARNING: locking bug in get_random_u8 syzbot
2024-11-16 23:29 ` Hillf Danton
2024-11-25 12:41 ` syzbot
2024-11-26 14:51   ` Sebastian Andrzej Siewior
2024-11-26 15:09     ` syzbot
2025-02-24 14:51 ` syzbot [this message]
2025-02-24 16:47   ` [syzbot] " Sebastian Andrzej Siewior

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=67bc8764.050a0220.bbfd1.0088.GAE@google.com \
    --to=syzbot+7f4f9a43a9c78eaee04f@syzkaller.appspotmail.com \
    --cc=Jason@zx2c4.com \
    --cc=bigeasy@linutronix.de \
    --cc=boqun.feng@gmail.com \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tytso@mit.edu \
    /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