From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+bd13648a53ed6933ca49@syzkaller.appspotmail.com>
Cc: gregkh@linuxfoundation.org, jack@suse.cz, lczerner@redhat.com,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, stable-commits@vger.kernel.org,
stable@kernel.org, stable@vger.kernel.org,
syzkaller-android-bugs@googlegroups.com,
tadeusz.struk@linaro.org, tytso@mit.edu
Subject: Re: kernel BUG in ext4_writepages
Date: Mon, 7 Nov 2022 15:08:59 +0100 [thread overview]
Message-ID: <20221107140859.lk7sok74nxs6srxe@quack3> (raw)
In-Reply-To: <000000000000bc92bf05ece0af6f@google.com>
On Mon 07-11-22 04:37:28, syzbot wrote:
> This bug is marked as fixed by commit:
> ext4: Avoid crash when inline data creation follows DIO write
> But I can't find it in any tested tree 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.
#syz fix: ext4: avoid crash when inline data creation follows DIO write
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2022-11-07 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000c3a53d05de992007@google.com>
2022-11-07 12:37 ` kernel BUG in ext4_writepages syzbot
2022-11-07 14:08 ` Jan Kara [this message]
2022-05-10 22:28 Tadeusz Struk
2022-05-19 12:23 ` Jan Kara
2022-05-19 15:40 ` Tadeusz Struk
2022-05-19 23:14 ` Tadeusz Struk
2022-05-20 9:50 ` Jan Kara
2022-05-20 14:50 ` Tadeusz Struk
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=20221107140859.lk7sok74nxs6srxe@quack3 \
--to=jack@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+bd13648a53ed6933ca49@syzkaller.appspotmail.com \
--cc=syzkaller-android-bugs@googlegroups.com \
--cc=tadeusz.struk@linaro.org \
--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).