From: syzbot <syzbot+f4582777a19ec422b517@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, eadavis@qq.com,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, nogikh@google.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] kernel BUG in ext4_write_inline_data
Date: Thu, 25 Jan 2024 19:41:11 -0800 [thread overview]
Message-ID: <000000000000376be5060fd11135@google.com> (raw)
In-Reply-To: <000000000000dfd6a105f71001d7@google.com>
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=f4582777a19ec422b517
---
[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
next prev parent reply other threads:[~2024-01-26 3:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 3:16 [syzbot] [ext4?] kernel BUG in ext4_write_inline_data syzbot
2023-05-22 20:07 ` syzbot
2023-09-06 8:46 ` [syzbot] " syzbot
2023-09-20 8:47 ` syzbot
2023-10-04 8:47 ` syzbot
2023-10-18 8:48 ` syzbot
2023-11-01 8:49 ` syzbot
2023-11-15 8:50 ` syzbot
2023-11-29 8:51 ` syzbot
2023-12-13 8:52 ` syzbot
2023-12-29 3:40 ` syzbot
2024-01-12 3:40 ` syzbot
2024-01-26 3:41 ` syzbot [this message]
2024-02-09 3:41 ` syzbot
2024-02-23 3:42 ` syzbot
2024-03-08 3:42 ` syzbot
2024-03-22 3:43 ` syzbot
2024-04-05 3:43 ` syzbot
2024-04-19 3:44 ` syzbot
2024-05-03 3:44 ` syzbot
2024-05-17 3:45 ` 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=000000000000376be5060fd11135@google.com \
--to=syzbot+f4582777a19ec422b517@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=eadavis@qq.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--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;
as well as URLs for NNTP newsgroup(s).