[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <000000000000195e9205de96e067@google.com>
Date: Mon, 09 May 2022 09:41:09 -0700
From: syzbot <syzbot+fcc629d1a1ae8d3fe8a5@...kaller.appspotmail.com>
To: adilger.kernel@...ger.ca, jack@...e.cz, linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com,
tadeusz.struk@...aro.org, tytso@....edu
Subject: Re: [syzbot] kernel BUG in ext4_ind_remove_space
syzbot suspects this issue was fixed by commit:
commit 2da376228a2427501feb9d15815a45dbdbdd753e
Author: Tadeusz Struk <tadeusz.struk@...aro.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
Powered by blists - more mailing lists