[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <000000000000e99a3e0606e0169e@google.com>
Date: Wed, 04 Oct 2023 01:49:47 -0700
From: syzbot <syzbot+bdab24d5bf96d57c50b0@...kaller.appspotmail.com>
To: adilger.kernel@...ger.ca, joneslee@...gle.com,
linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
nogikh@...gle.com, syzkaller-android-bugs@...glegroups.com,
syzkaller-bugs@...glegroups.com, tudor.ambarus@...aro.org,
tytso@....edu
Subject: Re: [syzbot] kernel BUG in __ext4_journal_stop
This bug is marked as fixed by commit:
ext4: fix race condition between buffer write and page_mkwrite
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=bdab24d5bf96d57c50b0
---
[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
Powered by blists - more mailing lists