From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+d1da16f03614058fdc48@syzkaller.appspotmail.com>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu
Subject: Re: [syzbot] kernel BUG in ext4_do_writepages
Date: Fri, 21 Jun 2024 18:09:42 +0200 [thread overview]
Message-ID: <20240621160942.4bfi56fgy6ycvtl4@quack3> (raw)
In-Reply-To: <0000000000000b3e69061b5b5762@google.com>
On Thu 20-06-24 17:16:16, syzbot wrote:
> 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=d1da16f03614058fdc48
This bug is still unfixed AFAIK as we realized the fixing commit is buggy
and there's no easy fix (inline_data feature has some difficult to address
problems). So can we 'syz unfix' this? :)
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-06-21 16:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 20:23 [syzbot] kernel BUG in ext4_do_writepages syzbot
2023-09-01 0:02 ` syzbot
2023-09-15 0:02 ` syzbot
2023-09-29 0:03 ` syzbot
2023-10-13 0:03 ` syzbot
2023-10-27 0:04 ` syzbot
2023-11-10 0:05 ` syzbot
2023-11-24 0:06 ` syzbot
2023-12-08 0:06 ` syzbot
2023-12-22 0:07 ` syzbot
2024-01-05 0:07 ` syzbot
2024-01-19 0:08 ` syzbot
2024-02-02 0:08 ` syzbot
2024-02-16 0:09 ` syzbot
2024-03-01 0:09 ` syzbot
2024-03-15 0:10 ` syzbot
2024-03-29 0:11 ` syzbot
2024-04-12 0:12 ` syzbot
2024-04-26 0:13 ` syzbot
2024-05-10 0:13 ` syzbot
2024-05-24 0:14 ` syzbot
2024-06-07 0:15 ` syzbot
2024-06-21 0:16 ` syzbot
2024-06-21 16:09 ` Jan Kara [this message]
2024-07-05 16:10 ` syzbot
2024-07-19 16:11 ` syzbot
2024-07-20 2:57 ` Baokun Li
2025-05-09 7:11 ` I Hsin Cheng
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=20240621160942.4bfi56fgy6ycvtl4@quack3 \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+d1da16f03614058fdc48@syzkaller.appspotmail.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