Re: WARNING in ext4_da_update_reserve_space

2020-04-04 Thread syzbot
Hello, syzbot has tested the proposed patch and the reproducer did not trigger crash: Reported-and-tested-by: syzbot+67e4f16db666b1c82...@syzkaller.appspotmail.com Tested on: commit: 54d3adbc ext4: save all error info in save_error_info() an.. git tree:

Re: WARNING in ext4_da_update_reserve_space

2020-04-04 Thread Theodore Y. Ts'o
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev I'm curious why this is only showing up as failing on next-next. Let's see if it fails on the ext4.git tree. >From the bisect logs syzbot is able to repro on all of v5.x and v4.20.0. However, I'm not able to repro it

Re: WARNING in ext4_da_update_reserve_space

2020-04-02 Thread Murilo Opsfelder Araújo
d-by: syzbot+67e4f16db666b1c82...@syzkaller.appspotmail.com > Fixes: 658b0f92bc70 ("powerpc/traps: Print unhandled signals in a separate > function") > > EXT4-fs warning (device sda1): ext4_da_update_reserve_space:344: > ext4_da_update_reserve_space: ino 15722, used 1 wit

WARNING in ext4_da_update_reserve_space

2020-04-02 Thread syzbot
gnals in a separate function") EXT4-fs warning (device sda1): ext4_da_update_reserve_space:344: ext4_da_update_reserve_space: ino 15722, used 1 with only 0 reserved data blocks [ cut here ] WARNING: CPU: 1 PID: 359 at fs/ext4/inode.c:348 ext4_da_update_reserve_space+0x62