Re: [syzbot] WARNING: ODEBUG bug in ext4_fill_super (3)
On Sat 13-03-21 20:08:14, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:28806e4d Merge tag 'media/v5.12-2' of git://git.kernel.org..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=136d1bbcd0
> kernel config: https://syzkaller.appspot.com/x/.config?x=6bcf96204c1b8e77
> dashboard link: https://syzkaller.appspot.com/bug?extid=628472a2aac693ab0fcd
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1133abfad0
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1191aab2d0
>
> The issue was bisected to:
>
> commit 2d01ddc86606564fb08c56e3bc93a0693895f710
> Author: Jan Kara
> Date: Wed Dec 16 10:18:40 2020 +
>
> ext4: save error info to sb through journal if available
After some head scratching I think [1] should fix the problem.
[1] https://lore.kernel.org/linux-ext4/20210315165906.2175-1-j...@suse.cz
Honza
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=152b9d56d0
> final oops: https://syzkaller.appspot.com/x/report.txt?x=172b9d56d0
> console output: https://syzkaller.appspot.com/x/log.txt?x=132b9d56d0
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+628472a2aac693ab0...@syzkaller.appspotmail.com
> Fixes: 2d01ddc86606 ("ext4: save error info to sb through journal if
> available")
>
> ODEBUG: free active (active state 0) object type: timer_list hint:
> print_daily_error_info+0x0/0x1f0 fs/ext4/super.c:1334
> WARNING: CPU: 1 PID: 12723 at lib/debugobjects.c:505
> debug_print_object+0x16e/0x250 lib/debugobjects.c:505
> Modules linked in:
> CPU: 0 PID: 12723 Comm: syz-executor932 Not tainted 5.12.0-rc2-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> RIP: 0010:debug_print_object+0x16e/0x250 lib/debugobjects.c:505
> Code: ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 af 00 00 00 48 8b 14 dd a0
> 06 c2 89 4c 89 ee 48 c7 c7 a0 fa c1 89 e8 fc 41 f8 04 <0f> 0b 83 05 05 7e fb
> 09 01 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e c3
> RSP: 0018:c9000e6ef980 EFLAGS: 00010286
>
> RAX: RBX: 0003 RCX:
> RDX: 88801d5e9bc0 RSI: 815c0d25 RDI: f52001cddf22
> RBP: 0001 R08: R09:
> R10: 815b9abe R11: R12: 896d7da0
> R13: 89c200e0 R14: 81629d00 R15: dc00
> FS: 00f93300() GS:8880b9c0() knlGS:
> CS: 0010 DS: ES: CR0: 80050033
> CR2: 7fcda3ec CR3: 155a1000 CR4: 00350ef0
> Call Trace:
> __debug_check_no_obj_freed lib/debugobjects.c:987 [inline]
> debug_check_no_obj_freed+0x301/0x420 lib/debugobjects.c:1018
> slab_free_hook mm/slub.c:1554 [inline]
> slab_free_freelist_hook+0x147/0x210 mm/slub.c:1600
> slab_free mm/slub.c:3161 [inline]
> kfree+0xe5/0x7f0 mm/slub.c:4213
> ext4_fill_super+0x84f/0xded0 fs/ext4/super.c:5182
> mount_bdev+0x34d/0x410 fs/super.c:1367
> legacy_get_tree+0x105/0x220 fs/fs_context.c:592
> vfs_get_tree+0x89/0x2f0 fs/super.c:1497
> do_new_mount fs/namespace.c:2903 [inline]
> path_mount+0x132a/0x1f90 fs/namespace.c:3233
> do_mount fs/namespace.c:3246 [inline]
> __do_sys_mount fs/namespace.c:3454 [inline]
> __se_sys_mount fs/namespace.c:3431 [inline]
> __x64_sys_mount+0x27f/0x300 fs/namespace.c:3431
> do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
> entry_SYSCALL_64_after_hwframe+0x44/0xae
> RIP: 0033:0x445c0a
> Code: 48 c7 c2 c0 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 a8 00 00 00
> 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73
> 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:7ffe8bf4c3b8 EFLAGS: 0202
> ORIG_RAX: 00a5
> RAX: ffda RBX: 7ffe8bf4c410 RCX: 00445c0a
> RDX: 2040 RSI: 2100 RDI: 7ffe8bf4c3d0
> RBP: 7ffe8bf4c3d0 R08: 7ffe8bf4c410 R09:
>
>
> ---
> This report is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkal...@googlegroups.com.
>
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
> syzbot can test patches for this issue, for details see:
> https://goo.gl/tpsmEJ#testing-patches
--
Jan Kara
SUSE Labs, CR
[syzbot] WARNING: ODEBUG bug in ext4_fill_super (3)
Hello,
syzbot found the following issue on:
HEAD commit:28806e4d Merge tag 'media/v5.12-2' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=136d1bbcd0
kernel config: https://syzkaller.appspot.com/x/.config?x=6bcf96204c1b8e77
dashboard link: https://syzkaller.appspot.com/bug?extid=628472a2aac693ab0fcd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1133abfad0
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1191aab2d0
The issue was bisected to:
commit 2d01ddc86606564fb08c56e3bc93a0693895f710
Author: Jan Kara
Date: Wed Dec 16 10:18:40 2020 +
ext4: save error info to sb through journal if available
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=152b9d56d0
final oops: https://syzkaller.appspot.com/x/report.txt?x=172b9d56d0
console output: https://syzkaller.appspot.com/x/log.txt?x=132b9d56d0
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+628472a2aac693ab0...@syzkaller.appspotmail.com
Fixes: 2d01ddc86606 ("ext4: save error info to sb through journal if available")
ODEBUG: free active (active state 0) object type: timer_list hint:
print_daily_error_info+0x0/0x1f0 fs/ext4/super.c:1334
WARNING: CPU: 1 PID: 12723 at lib/debugobjects.c:505
debug_print_object+0x16e/0x250 lib/debugobjects.c:505
Modules linked in:
CPU: 0 PID: 12723 Comm: syz-executor932 Not tainted 5.12.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google
01/01/2011
RIP: 0010:debug_print_object+0x16e/0x250 lib/debugobjects.c:505
Code: ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 af 00 00 00 48 8b 14 dd a0
06 c2 89 4c 89 ee 48 c7 c7 a0 fa c1 89 e8 fc 41 f8 04 <0f> 0b 83 05 05 7e fb 09
01 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e c3
RSP: 0018:c9000e6ef980 EFLAGS: 00010286
RAX: RBX: 0003 RCX:
RDX: 88801d5e9bc0 RSI: 815c0d25 RDI: f52001cddf22
RBP: 0001 R08: R09:
R10: 815b9abe R11: R12: 896d7da0
R13: 89c200e0 R14: 81629d00 R15: dc00
FS: 00f93300() GS:8880b9c0() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 7fcda3ec CR3: 155a1000 CR4: 00350ef0
Call Trace:
__debug_check_no_obj_freed lib/debugobjects.c:987 [inline]
debug_check_no_obj_freed+0x301/0x420 lib/debugobjects.c:1018
slab_free_hook mm/slub.c:1554 [inline]
slab_free_freelist_hook+0x147/0x210 mm/slub.c:1600
slab_free mm/slub.c:3161 [inline]
kfree+0xe5/0x7f0 mm/slub.c:4213
ext4_fill_super+0x84f/0xded0 fs/ext4/super.c:5182
mount_bdev+0x34d/0x410 fs/super.c:1367
legacy_get_tree+0x105/0x220 fs/fs_context.c:592
vfs_get_tree+0x89/0x2f0 fs/super.c:1497
do_new_mount fs/namespace.c:2903 [inline]
path_mount+0x132a/0x1f90 fs/namespace.c:3233
do_mount fs/namespace.c:3246 [inline]
__do_sys_mount fs/namespace.c:3454 [inline]
__se_sys_mount fs/namespace.c:3431 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3431
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x445c0a
Code: 48 c7 c2 c0 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 a8 00 00 00
0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01
c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:7ffe8bf4c3b8 EFLAGS: 0202
ORIG_RAX: 00a5
RAX: ffda RBX: 7ffe8bf4c410 RCX: 00445c0a
RDX: 2040 RSI: 2100 RDI: 7ffe8bf4c3d0
RBP: 7ffe8bf4c3d0 R08: 7ffe8bf4c410 R09:
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkal...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
Re: WARNING: ODEBUG bug in ext4_fill_super (2)
#syz dup: general protection fault in ext4_commit_super
On Mon 21-12-20 23:54:18, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:0d52778b Add linux-next specific files for 20201218
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1619061350
> kernel config: https://syzkaller.appspot.com/x/.config?x=5c81cc44aa25b5b3
> dashboard link: https://syzkaller.appspot.com/bug?extid=3002ac6b4fd242a64228
> compiler: gcc (GCC) 10.1.0-syz 20200507
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=128f512350
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14f9f30f50
>
> The issue was bisected to:
>
> commit e810c942a325cf749e859d7aa3a43dc219cea299
> Author: Jan Kara
> Date: Wed Dec 16 10:18:40 2020 +
>
> ext4: save error info to sb through journal if available
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12d9df0750
> final oops: https://syzkaller.appspot.com/x/report.txt?x=11d9df0750
> console output: https://syzkaller.appspot.com/x/log.txt?x=16d9df0750
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+3002ac6b4fd242a64...@syzkaller.appspotmail.com
> Fixes: e810c942a325 ("ext4: save error info to sb through journal if
> available")
>
> EXT4-fs error (device loop3): ext4_fill_super:4943: inode #2: comm
> syz-executor723: iget: root inode unallocated
> EXT4-fs (loop3): get root inode failed
> EXT4-fs (loop3): mount failed
> [ cut here ]
> ODEBUG: free active (active state 0) object type: work_struct hint:
> flush_stashed_error_work+0x0/0x2a0 fs/ext4/ext4.h:2040
> WARNING: CPU: 0 PID: 13670 at lib/debugobjects.c:505
> debug_print_object+0x16e/0x250 lib/debugobjects.c:505
> Modules linked in:
> CPU: 0 PID: 13670 Comm: syz-executor723 Not tainted
> 5.10.0-next-20201218-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> RIP: 0010:debug_print_object+0x16e/0x250 lib/debugobjects.c:505
> Code: ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 af 00 00 00 48 8b 14 dd 20
> af bf 89 4c 89 ee 48 c7 c7 20 a3 bf 89 e8 30 78 05 05 <0f> 0b 83 05 55 8a b9
> 09 01 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e c3
> RSP: 0018:c90001d0f9b8 EFLAGS: 00010282
> RAX: RBX: 0003 RCX:
> RDX: 888024b63600 RSI: 815b95f5 RDI: f520003a1f29
> RBP: 0001 R08: R09:
> R10: 815b7a4b R11: R12: 896ae040
> R13: 89bfa920 R14: 814911f0 R15: dc00
> FS: 0163a940() GS:8880b9c0() knlGS:
> CS: 0010 DS: ES: CR0: 80050033
> CR2: 0043fb60 CR3: 1226b000 CR4: 001506f0
> DR0: DR1: DR2:
> DR3: DR6: fffe0ff0 DR7: 0400
> Call Trace:
> __debug_check_no_obj_freed lib/debugobjects.c:987 [inline]
> debug_check_no_obj_freed+0x309/0x430 lib/debugobjects.c:1018
> slab_free_hook mm/slub.c:1540 [inline]
> slab_free_freelist_hook+0x12b/0x1d0 mm/slub.c:1586
> slab_free mm/slub.c:3157 [inline]
> kfree+0xdb/0x3c0 mm/slub.c:4156
> ext4_fill_super+0x86c/0xdf40 fs/ext4/super.c:5174
> mount_bdev+0x34d/0x410 fs/super.c:1366
> legacy_get_tree+0x105/0x220 fs/fs_context.c:592
> vfs_get_tree+0x89/0x2f0 fs/super.c:1496
> do_new_mount fs/namespace.c:2896 [inline]
> path_mount+0x12ae/0x1e70 fs/namespace.c:3227
> do_mount fs/namespace.c:3240 [inline]
> __do_sys_mount fs/namespace.c:3448 [inline]
> __se_sys_mount fs/namespace.c:3425 [inline]
> __x64_sys_mount+0x27f/0x300 fs/namespace.c:3425
> do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
> entry_SYSCALL_64_after_hwframe+0x44/0xa9
> RIP: 0033:0x44873a
> Code: b8 08 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 cd a2 fb ff c3 66 2e 0f 1f
> 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f
> 83 aa a2 fb ff c3 66 0f 1f 84 00 00 00 00 00
> RSP: 002b:7fff16496da8 EFLAGS: 0202 ORIG_RAX: 00a5
> RAX: ffda RBX: 7fff16496e00 RCX: 0044873a
> RDX: 2000 RSI: 2100 RDI: 7fff16496dc0
> RBP: 7fff16496dc0 R08: 7fff16496e00 R09:
> R10: R11: 0202 R12: 0006
> R13: 0005 R14: 0004 R15: 0004
>
>
> ---
> This report is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkal...@googlegroups.com.
>
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
> syzbot can test patches for this issue, for
WARNING: ODEBUG bug in ext4_fill_super (2)
Hello,
syzbot found the following issue on:
HEAD commit:0d52778b Add linux-next specific files for 20201218
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1619061350
kernel config: https://syzkaller.appspot.com/x/.config?x=5c81cc44aa25b5b3
dashboard link: https://syzkaller.appspot.com/bug?extid=3002ac6b4fd242a64228
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=128f512350
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14f9f30f50
The issue was bisected to:
commit e810c942a325cf749e859d7aa3a43dc219cea299
Author: Jan Kara
Date: Wed Dec 16 10:18:40 2020 +
ext4: save error info to sb through journal if available
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12d9df0750
final oops: https://syzkaller.appspot.com/x/report.txt?x=11d9df0750
console output: https://syzkaller.appspot.com/x/log.txt?x=16d9df0750
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3002ac6b4fd242a64...@syzkaller.appspotmail.com
Fixes: e810c942a325 ("ext4: save error info to sb through journal if available")
EXT4-fs error (device loop3): ext4_fill_super:4943: inode #2: comm
syz-executor723: iget: root inode unallocated
EXT4-fs (loop3): get root inode failed
EXT4-fs (loop3): mount failed
[ cut here ]
ODEBUG: free active (active state 0) object type: work_struct hint:
flush_stashed_error_work+0x0/0x2a0 fs/ext4/ext4.h:2040
WARNING: CPU: 0 PID: 13670 at lib/debugobjects.c:505
debug_print_object+0x16e/0x250 lib/debugobjects.c:505
Modules linked in:
CPU: 0 PID: 13670 Comm: syz-executor723 Not tainted
5.10.0-next-20201218-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google
01/01/2011
RIP: 0010:debug_print_object+0x16e/0x250 lib/debugobjects.c:505
Code: ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 af 00 00 00 48 8b 14 dd 20
af bf 89 4c 89 ee 48 c7 c7 20 a3 bf 89 e8 30 78 05 05 <0f> 0b 83 05 55 8a b9 09
01 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e c3
RSP: 0018:c90001d0f9b8 EFLAGS: 00010282
RAX: RBX: 0003 RCX:
RDX: 888024b63600 RSI: 815b95f5 RDI: f520003a1f29
RBP: 0001 R08: R09:
R10: 815b7a4b R11: R12: 896ae040
R13: 89bfa920 R14: 814911f0 R15: dc00
FS: 0163a940() GS:8880b9c0() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 0043fb60 CR3: 1226b000 CR4: 001506f0
DR0: DR1: DR2:
DR3: DR6: fffe0ff0 DR7: 0400
Call Trace:
__debug_check_no_obj_freed lib/debugobjects.c:987 [inline]
debug_check_no_obj_freed+0x309/0x430 lib/debugobjects.c:1018
slab_free_hook mm/slub.c:1540 [inline]
slab_free_freelist_hook+0x12b/0x1d0 mm/slub.c:1586
slab_free mm/slub.c:3157 [inline]
kfree+0xdb/0x3c0 mm/slub.c:4156
ext4_fill_super+0x86c/0xdf40 fs/ext4/super.c:5174
mount_bdev+0x34d/0x410 fs/super.c:1366
legacy_get_tree+0x105/0x220 fs/fs_context.c:592
vfs_get_tree+0x89/0x2f0 fs/super.c:1496
do_new_mount fs/namespace.c:2896 [inline]
path_mount+0x12ae/0x1e70 fs/namespace.c:3227
do_mount fs/namespace.c:3240 [inline]
__do_sys_mount fs/namespace.c:3448 [inline]
__se_sys_mount fs/namespace.c:3425 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3425
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x44873a
Code: b8 08 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 cd a2 fb ff c3 66 2e 0f 1f
84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83
aa a2 fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:7fff16496da8 EFLAGS: 0202 ORIG_RAX: 00a5
RAX: ffda RBX: 7fff16496e00 RCX: 0044873a
RDX: 2000 RSI: 2100 RDI: 7fff16496dc0
RBP: 7fff16496dc0 R08: 7fff16496e00 R09:
R10: R11: 0202 R12: 0006
R13: 0005 R14: 0004 R15: 0004
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkal...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
Re: WARNING: ODEBUG bug in ext4_fill_super
On Fri, Aug 30, 2019 at 12:46:21PM -0700, 'Dmitry Vyukov' via syzkaller-bugs wrote: > On Fri, Aug 30, 2019 at 12:42 PM 'Nick Desaulniers' via syzkaller-bugs > wrote: > > > > Dmitry, > > Any idea how clang-built-linux got CC'ed on this? Is syzcaller > > running clang builds, yet? (this looks like a GCC build) > > syzbot always uses get_maintainers: > > $ ./scripts/get_maintainer.pl -f fs/ext4/super.c > "Theodore Ts'o" (maintainer:EXT4 FILE SYSTEM) > Andreas Dilger (maintainer:EXT4 FILE SYSTEM) > linux-e...@vger.kernel.org (open list:EXT4 FILE SYSTEM) > linux-kernel@vger.kernel.org (open list) > clang-built-li...@googlegroups.com (open list:CLANG/LLVM BUILD SUPPORT) > CLANG/LLVM BUILD SUPPORT L: clang-built-li...@googlegroups.com W: https://clangbuiltlinux.github.io/ B: https://github.com/ClangBuiltLinux/linux/issues C: irc://chat.freenode.net/clangbuiltlinux S: Supported K: \b(?i:clang|llvm)\b So, clang-built-linux has volunteered to maintain every file that contains the word "clang" or "llvm" anywhere in its contents :-) $ grep clang fs/ext4/super.c (void) ei; /* shut up clang warning if !CONFIG_LOCKDEP */ - Eric
Re: WARNING: ODEBUG bug in ext4_fill_super
#syz invalid This has already been fixed in the latest linux-next
Re: WARNING: ODEBUG bug in ext4_fill_super
On Fri, Aug 30, 2019 at 12:42 PM 'Nick Desaulniers' via syzkaller-bugs wrote: > > Dmitry, > Any idea how clang-built-linux got CC'ed on this? Is syzcaller > running clang builds, yet? (this looks like a GCC build) syzbot always uses get_maintainers: $ ./scripts/get_maintainer.pl -f fs/ext4/super.c "Theodore Ts'o" (maintainer:EXT4 FILE SYSTEM) Andreas Dilger (maintainer:EXT4 FILE SYSTEM) linux-e...@vger.kernel.org (open list:EXT4 FILE SYSTEM) linux-kernel@vger.kernel.org (open list) clang-built-li...@googlegroups.com (open list:CLANG/LLVM BUILD SUPPORT) > On Fri, Aug 30, 2019 at 12:39 PM syzbot > wrote: > > > > Hello, > > > > syzbot found the following crash on: > > > > HEAD commit:ed858b88 Add linux-next specific files for 20190826 > > git tree: linux-next > > console output: https://syzkaller.appspot.com/x/log.txt?x=14209eca60 > > kernel config: https://syzkaller.appspot.com/x/.config?x=ee8373cd9733e305 > > dashboard link: https://syzkaller.appspot.com/bug?extid=0bf8ddafbdf2c46eb6f3 > > compiler: gcc (GCC) 9.0.0 20181231 (experimental) > > > > Unfortunately, I don't have any reproducer for this crash yet. > > > > IMPORTANT: if you fix the bug, please add the following tag to the commit: > > Reported-by: syzbot+0bf8ddafbdf2c46eb...@syzkaller.appspotmail.com > > > > EXT4-fs (loop2): corrupt root inode, run e2fsck > > EXT4-fs (loop2): mount failed > > [ cut here ] > > ODEBUG: free active (active state 0) object type: percpu_counter hint: 0x0 > > WARNING: CPU: 0 PID: 12342 at lib/debugobjects.c:481 > > debug_print_object+0x168/0x250 lib/debugobjects.c:481 > > Kernel panic - not syncing: panic_on_warn set ... > > CPU: 0 PID: 12342 Comm: syz-executor.2 Not tainted 5.3.0-rc6-next-20190826 > > #73 > > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS > > Google 01/01/2011 > > Call Trace: > > __dump_stack lib/dump_stack.c:77 [inline] > > dump_stack+0x172/0x1f0 lib/dump_stack.c:113 > > panic+0x2dc/0x755 kernel/panic.c:220 > > __warn.cold+0x2f/0x3c kernel/panic.c:581 > > report_bug+0x289/0x300 lib/bug.c:195 > > fixup_bug arch/x86/kernel/traps.c:179 [inline] > > fixup_bug arch/x86/kernel/traps.c:174 [inline] > > do_error_trap+0x11b/0x200 arch/x86/kernel/traps.c:272 > > do_invalid_op+0x37/0x50 arch/x86/kernel/traps.c:291 > > invalid_op+0x23/0x30 arch/x86/entry/entry_64.S:1028 > > RIP: 0010:debug_print_object+0x168/0x250 lib/debugobjects.c:481 > > Code: dd 60 6c e6 87 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 b5 00 00 00 48 > > 8b 14 dd 60 6c e6 87 48 c7 c7 c0 61 e6 87 e8 20 31 01 fe <0f> 0b 83 05 f3 > > 67 83 06 01 48 83 c4 20 5b 41 5c 41 5d 41 5e 5d c3 > > RSP: 0018:88806c9ff938 EFLAGS: 00010086 > > RAX: RBX: 0003 RCX: > > RDX: 0004 RSI: 815bd606 RDI: ed100d93ff19 > > RBP: 88806c9ff978 R08: 888067d48140 R09: ed1015d04109 > > R10: ed1015d04108 R11: 8880ae820847 R12: 0001 > > R13: 8935e800 R14: R15: 88806903c818 > > __debug_check_no_obj_freed lib/debugobjects.c:963 [inline] > > debug_check_no_obj_freed+0x2d4/0x43f lib/debugobjects.c:994 > > kfree+0xf8/0x2c0 mm/slab.c:3755 > > ext4_fill_super+0x8cb/0xcc80 fs/ext4/super.c:4684 > > mount_bdev+0x304/0x3c0 fs/super.c:1407 > > ext4_mount+0x35/0x40 fs/ext4/super.c:6019 > > legacy_get_tree+0x113/0x220 fs/fs_context.c:651 > > vfs_get_tree+0x8f/0x380 fs/super.c:1482 > > do_new_mount fs/namespace.c:2796 [inline] > > do_mount+0x13b3/0x1c30 fs/namespace.c:3116 > > ksys_mount+0xdb/0x150 fs/namespace.c:3325 > > __do_sys_mount fs/namespace.c:3339 [inline] > > __se_sys_mount fs/namespace.c:3336 [inline] > > __x64_sys_mount+0xbe/0x150 fs/namespace.c:3336 > > do_syscall_64+0xfa/0x760 arch/x86/entry/common.c:290 > > entry_SYSCALL_64_after_hwframe+0x49/0xbe > > RIP: 0033:0x45c2ca > > Code: b8 a6 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 9d 8d fb ff c3 66 2e 0f > > 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff > > ff 0f 83 7a 8d fb ff c3 66 0f 1f 84 00 00 00 00 00 > > RSP: 002b:7fa684517a88 EFLAGS: 0206 ORIG_RAX: 00a5 > > RAX: ffda RBX: 7fa684517b40 RCX: 0045c2ca > > RDX: 7fa684517ae0 RSI: 2000 RDI: 7fa684517b00 > > RBP: 1000 R08: 7fa684517b40 R09: 7fa684517ae0 > > R10: 0001 R11: 0206 R12: 0003 > > R13: 004c89d6 R14: 004df8f8 R15: > > Kernel Offset: disabled > > Rebooting in 86400 seconds.. > > > > > > --- > > This bug is generated by a bot. It may contain errors. > > See https://goo.gl/tpsmEJ for more information about syzbot. > > syzbot engineers can be reached at syzkal...@googlegroups.com. > > > > syzbot will keep track of this bug report. See: > > https://goo.gl/tpsmEJ#status for how to communicate with syzbot. > > > > -- > > You received this message
Re: WARNING: ODEBUG bug in ext4_fill_super
Dmitry, Any idea how clang-built-linux got CC'ed on this? Is syzcaller running clang builds, yet? (this looks like a GCC build) On Fri, Aug 30, 2019 at 12:39 PM syzbot wrote: > > Hello, > > syzbot found the following crash on: > > HEAD commit:ed858b88 Add linux-next specific files for 20190826 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=14209eca60 > kernel config: https://syzkaller.appspot.com/x/.config?x=ee8373cd9733e305 > dashboard link: https://syzkaller.appspot.com/bug?extid=0bf8ddafbdf2c46eb6f3 > compiler: gcc (GCC) 9.0.0 20181231 (experimental) > > Unfortunately, I don't have any reproducer for this crash yet. > > IMPORTANT: if you fix the bug, please add the following tag to the commit: > Reported-by: syzbot+0bf8ddafbdf2c46eb...@syzkaller.appspotmail.com > > EXT4-fs (loop2): corrupt root inode, run e2fsck > EXT4-fs (loop2): mount failed > [ cut here ] > ODEBUG: free active (active state 0) object type: percpu_counter hint: 0x0 > WARNING: CPU: 0 PID: 12342 at lib/debugobjects.c:481 > debug_print_object+0x168/0x250 lib/debugobjects.c:481 > Kernel panic - not syncing: panic_on_warn set ... > CPU: 0 PID: 12342 Comm: syz-executor.2 Not tainted 5.3.0-rc6-next-20190826 > #73 > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS > Google 01/01/2011 > Call Trace: > __dump_stack lib/dump_stack.c:77 [inline] > dump_stack+0x172/0x1f0 lib/dump_stack.c:113 > panic+0x2dc/0x755 kernel/panic.c:220 > __warn.cold+0x2f/0x3c kernel/panic.c:581 > report_bug+0x289/0x300 lib/bug.c:195 > fixup_bug arch/x86/kernel/traps.c:179 [inline] > fixup_bug arch/x86/kernel/traps.c:174 [inline] > do_error_trap+0x11b/0x200 arch/x86/kernel/traps.c:272 > do_invalid_op+0x37/0x50 arch/x86/kernel/traps.c:291 > invalid_op+0x23/0x30 arch/x86/entry/entry_64.S:1028 > RIP: 0010:debug_print_object+0x168/0x250 lib/debugobjects.c:481 > Code: dd 60 6c e6 87 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 b5 00 00 00 48 > 8b 14 dd 60 6c e6 87 48 c7 c7 c0 61 e6 87 e8 20 31 01 fe <0f> 0b 83 05 f3 > 67 83 06 01 48 83 c4 20 5b 41 5c 41 5d 41 5e 5d c3 > RSP: 0018:88806c9ff938 EFLAGS: 00010086 > RAX: RBX: 0003 RCX: > RDX: 0004 RSI: 815bd606 RDI: ed100d93ff19 > RBP: 88806c9ff978 R08: 888067d48140 R09: ed1015d04109 > R10: ed1015d04108 R11: 8880ae820847 R12: 0001 > R13: 8935e800 R14: R15: 88806903c818 > __debug_check_no_obj_freed lib/debugobjects.c:963 [inline] > debug_check_no_obj_freed+0x2d4/0x43f lib/debugobjects.c:994 > kfree+0xf8/0x2c0 mm/slab.c:3755 > ext4_fill_super+0x8cb/0xcc80 fs/ext4/super.c:4684 > mount_bdev+0x304/0x3c0 fs/super.c:1407 > ext4_mount+0x35/0x40 fs/ext4/super.c:6019 > legacy_get_tree+0x113/0x220 fs/fs_context.c:651 > vfs_get_tree+0x8f/0x380 fs/super.c:1482 > do_new_mount fs/namespace.c:2796 [inline] > do_mount+0x13b3/0x1c30 fs/namespace.c:3116 > ksys_mount+0xdb/0x150 fs/namespace.c:3325 > __do_sys_mount fs/namespace.c:3339 [inline] > __se_sys_mount fs/namespace.c:3336 [inline] > __x64_sys_mount+0xbe/0x150 fs/namespace.c:3336 > do_syscall_64+0xfa/0x760 arch/x86/entry/common.c:290 > entry_SYSCALL_64_after_hwframe+0x49/0xbe > RIP: 0033:0x45c2ca > Code: b8 a6 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 9d 8d fb ff c3 66 2e 0f > 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff > ff 0f 83 7a 8d fb ff c3 66 0f 1f 84 00 00 00 00 00 > RSP: 002b:7fa684517a88 EFLAGS: 0206 ORIG_RAX: 00a5 > RAX: ffda RBX: 7fa684517b40 RCX: 0045c2ca > RDX: 7fa684517ae0 RSI: 2000 RDI: 7fa684517b00 > RBP: 1000 R08: 7fa684517b40 R09: 7fa684517ae0 > R10: 0001 R11: 0206 R12: 0003 > R13: 004c89d6 R14: 004df8f8 R15: > Kernel Offset: disabled > Rebooting in 86400 seconds.. > > > --- > This bug is generated by a bot. It may contain errors. > See https://goo.gl/tpsmEJ for more information about syzbot. > syzbot engineers can be reached at syzkal...@googlegroups.com. > > syzbot will keep track of this bug report. See: > https://goo.gl/tpsmEJ#status for how to communicate with syzbot. > > -- > You received this message because you are subscribed to the Google Groups > "Clang Built Linux" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clang-built-linux+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/clang-built-linux/6fc70605915ac6ad%40google.com. -- Thanks, ~Nick Desaulniers
WARNING: ODEBUG bug in ext4_fill_super
Hello, syzbot found the following crash on: HEAD commit:ed858b88 Add linux-next specific files for 20190826 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=14209eca60 kernel config: https://syzkaller.appspot.com/x/.config?x=ee8373cd9733e305 dashboard link: https://syzkaller.appspot.com/bug?extid=0bf8ddafbdf2c46eb6f3 compiler: gcc (GCC) 9.0.0 20181231 (experimental) Unfortunately, I don't have any reproducer for this crash yet. IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+0bf8ddafbdf2c46eb...@syzkaller.appspotmail.com EXT4-fs (loop2): corrupt root inode, run e2fsck EXT4-fs (loop2): mount failed [ cut here ] ODEBUG: free active (active state 0) object type: percpu_counter hint: 0x0 WARNING: CPU: 0 PID: 12342 at lib/debugobjects.c:481 debug_print_object+0x168/0x250 lib/debugobjects.c:481 Kernel panic - not syncing: panic_on_warn set ... CPU: 0 PID: 12342 Comm: syz-executor.2 Not tainted 5.3.0-rc6-next-20190826 #73 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x172/0x1f0 lib/dump_stack.c:113 panic+0x2dc/0x755 kernel/panic.c:220 __warn.cold+0x2f/0x3c kernel/panic.c:581 report_bug+0x289/0x300 lib/bug.c:195 fixup_bug arch/x86/kernel/traps.c:179 [inline] fixup_bug arch/x86/kernel/traps.c:174 [inline] do_error_trap+0x11b/0x200 arch/x86/kernel/traps.c:272 do_invalid_op+0x37/0x50 arch/x86/kernel/traps.c:291 invalid_op+0x23/0x30 arch/x86/entry/entry_64.S:1028 RIP: 0010:debug_print_object+0x168/0x250 lib/debugobjects.c:481 Code: dd 60 6c e6 87 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 b5 00 00 00 48 8b 14 dd 60 6c e6 87 48 c7 c7 c0 61 e6 87 e8 20 31 01 fe <0f> 0b 83 05 f3 67 83 06 01 48 83 c4 20 5b 41 5c 41 5d 41 5e 5d c3 RSP: 0018:88806c9ff938 EFLAGS: 00010086 RAX: RBX: 0003 RCX: RDX: 0004 RSI: 815bd606 RDI: ed100d93ff19 RBP: 88806c9ff978 R08: 888067d48140 R09: ed1015d04109 R10: ed1015d04108 R11: 8880ae820847 R12: 0001 R13: 8935e800 R14: R15: 88806903c818 __debug_check_no_obj_freed lib/debugobjects.c:963 [inline] debug_check_no_obj_freed+0x2d4/0x43f lib/debugobjects.c:994 kfree+0xf8/0x2c0 mm/slab.c:3755 ext4_fill_super+0x8cb/0xcc80 fs/ext4/super.c:4684 mount_bdev+0x304/0x3c0 fs/super.c:1407 ext4_mount+0x35/0x40 fs/ext4/super.c:6019 legacy_get_tree+0x113/0x220 fs/fs_context.c:651 vfs_get_tree+0x8f/0x380 fs/super.c:1482 do_new_mount fs/namespace.c:2796 [inline] do_mount+0x13b3/0x1c30 fs/namespace.c:3116 ksys_mount+0xdb/0x150 fs/namespace.c:3325 __do_sys_mount fs/namespace.c:3339 [inline] __se_sys_mount fs/namespace.c:3336 [inline] __x64_sys_mount+0xbe/0x150 fs/namespace.c:3336 do_syscall_64+0xfa/0x760 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x45c2ca Code: b8 a6 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 9d 8d fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 7a 8d fb ff c3 66 0f 1f 84 00 00 00 00 00 RSP: 002b:7fa684517a88 EFLAGS: 0206 ORIG_RAX: 00a5 RAX: ffda RBX: 7fa684517b40 RCX: 0045c2ca RDX: 7fa684517ae0 RSI: 2000 RDI: 7fa684517b00 RBP: 1000 R08: 7fa684517b40 R09: 7fa684517ae0 R10: 0001 R11: 0206 R12: 0003 R13: 004c89d6 R14: 004df8f8 R15: Kernel Offset: disabled Rebooting in 86400 seconds.. --- This bug is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkal...@googlegroups.com. syzbot will keep track of this bug report. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
