[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <67bc8764.050a0220.bbfd1.0088.GAE@google.com>
Date: Mon, 24 Feb 2025 06:51:16 -0800
From: syzbot <syzbot+7f4f9a43a9c78eaee04f@...kaller.appspotmail.com>
To: Jason@...c4.com, bigeasy@...utronix.de, boqun.feng@...il.com,
hdanton@...a.com, jason@...c4.com, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com, tytso@....edu
Subject: Re: [syzbot] WARNING: locking bug in get_random_u8
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
Powered by blists - more mailing lists