From: "Theodore Ts'o" <tytso@mit.edu>
To: syzbot <syzbot+15cd994e273307bf5cfa@syzkaller.appspotmail.com>
Cc: adilger.kernel@dilger.ca, gregkh@linuxfoundation.org,
lczerner@redhat.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, sashal@kernel.org,
stable@vger.kernel.org, syzkaller-android-bugs@googlegroups.com,
tadeusz.struk@linaro.org
Subject: Re: kernel BUG in ext4_free_blocks (2)
Date: Thu, 15 Dec 2022 21:11:22 -0500 [thread overview]
Message-ID: <Y5vTyjRX6ZgIYxgj@mit.edu> (raw)
In-Reply-To: <000000000000b60c1105efe06dea@google.com>
On Thu, Dec 15, 2022 at 08:34:35AM -0800, syzbot wrote:
> This bug is marked as fixed by commit:
> ext4: block range must be validated before use in ext4_mb_clear_bb()
> 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.
I don't know what is going on with syzkaller's commit detection, but
commit 1e1c2b86ef86 ("ext4: block range must be validated before use
in ext4_mb_clear_bb()") is an exact match for the commit title, and
it's been in the upstream kernel since v6.0.
How do we make syzkaller accept this? I'll try this again, but I
don't hold out much hope.
#syz fix: ext4: block range must be validated before use in ext4_mb_clear_bb()
Syzkaller, go home, you're drunk.
- Ted
next prev parent reply other threads:[~2022-12-16 2:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000006c411605e2f127e5@google.com>
2022-10-20 16:32 ` syzbot
2022-11-03 16:33 ` syzbot
2022-11-17 16:34 ` syzbot
2022-12-01 16:34 ` syzbot
2022-12-15 16:34 ` syzbot
2022-12-16 2:11 ` Theodore Ts'o [this message]
2022-12-16 13:01 ` Lee Jones
2022-12-16 14:09 ` Aleksandr Nogikh
2022-12-16 14:12 ` Lee Jones
2022-12-16 17:04 ` Theodore Ts'o
2022-12-16 17:14 ` Aleksandr Nogikh
2022-12-16 18:45 ` Theodore Ts'o
2022-12-19 16:12 ` Aleksandr Nogikh
2022-12-19 18:15 ` Theodore Ts'o
2022-12-21 11:34 ` Aleksandr Nogikh
2023-01-04 11:34 ` syzbot
2023-01-18 12:45 ` syzbot
2023-02-01 12:45 ` syzbot
2023-02-15 12:45 ` [Android 5.10] " syzbot
2023-03-01 12:46 ` syzbot
2023-03-01 13:51 ` Tudor Ambarus
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=Y5vTyjRX6ZgIYxgj@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=gregkh@linuxfoundation.org \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+15cd994e273307bf5cfa@syzkaller.appspotmail.com \
--cc=syzkaller-android-bugs@googlegroups.com \
--cc=tadeusz.struk@linaro.org \
/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
all inboxes | Powered by JetHome®