From: syzbot <syzbot+fcc629d1a1ae8d3fe8a5@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, jack@suse.cz,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tadeusz.struk@linaro.org,
tytso@mit.edu
Subject: Re: [syzbot] kernel BUG in ext4_ind_remove_space
Date: Mon, 09 May 2022 09:41:09 -0700 [thread overview]
Message-ID: <000000000000195e9205de96e067@google.com> (raw)
In-Reply-To: <000000000000183d9e05d7f0c0ee@google.com>
syzbot suspects this issue was fixed by commit:
commit 2da376228a2427501feb9d15815a45dbdbdd753e
Author: Tadeusz Struk <tadeusz.struk@linaro.org>
Date: Thu Mar 31 20:05:15 2022 +0000
ext4: limit length to bitmap_maxbytes - blocksize in punch_hole
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=100ac712f00000
start commit: 09688c0166e7 Linux 5.17-rc8
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=d35f9bc6884af6c9
dashboard link: https://syzkaller.appspot.com/bug?extid=fcc629d1a1ae8d3fe8a5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1205b189700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15dda4fe700000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ext4: limit length to bitmap_maxbytes - blocksize in punch_hole
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-05-09 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 1:58 [syzbot] kernel BUG in ext4_ind_remove_space syzbot
2022-03-15 15:14 ` syzbot
2022-03-15 19:21 ` Tadeusz Struk
2022-03-15 20:22 ` syzbot
2022-03-15 21:38 ` [PATCH v2] ext4: check if offset+length is within valid fallocate Tadeusz Struk
2022-03-15 21:48 ` [syzbot] kernel BUG in ext4_ind_remove_space syzbot
2022-04-28 14:02 ` [PATCH v2] ext4: check if offset+length is within valid fallocate Jan Kara
2022-05-04 14:08 ` Tadeusz Struk
2022-05-09 16:41 ` syzbot [this message]
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=000000000000195e9205de96e067@google.com \
--to=syzbot+fcc629d1a1ae8d3fe8a5@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.