BUG: corrupted list in __es_insert_extent

8 views
Skip to first unread message

syzbot

unread,
Mar 10, 2019, 1:52:05 PM3/10/19
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: cf08baa2 Add linux-next specific files for 20190306
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=164e10cf200000
kernel config: https://syzkaller.appspot.com/x/.config?x=c8b6073d992e8217
dashboard link: https://syzkaller.appspot.com/bug?extid=ba1caa9aa151e26e5622
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
userspace arch: amd64
CC: [adilger...@dilger.ca linux...@vger.kernel.org
linux-...@vger.kernel.org ty...@mit.edu]

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+ba1caa...@syzkaller.appspotmail.com

list_add corruption. prev->next should be next (ffff88821671cc90), but was
ffffffff81a4d738. (prev=ffff8880851d2d70).
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:26!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 18166 Comm: udevd Not tainted 5.0.0-next-20190306 #4
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__list_add_valid.cold+0x3a/0x3c lib/list_debug.c:26
Code: 0b 48 89 f2 4c 89 e1 4c 89 ee 48 c7 c7 c0 dc a1 87 e8 29 9c 29 fe 0f
0b 48 89 f1 48 c7 c7 40 dc a1 87 4c 89 e6 e8 15 9c 29 fe <0f> 0b 4c 89 f6
48 c7 c7 e0 dd a1 87 e8 04 9c 29 fe 0f 0b 4c 89 ea
RSP: 0018:ffff888055237110 EFLAGS: 00010286
RAX: 0000000000000075 RBX: ffff88821671c6c0 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff815b0096 RDI: ffffed100aa46e14
RBP: ffff888055237128 R08: 0000000000000075 R09: ffffed1015d25011
R10: ffffed1015d25010 R11: ffff8880ae928087 R12: ffff88821671cc90
R13: ffff8880a0d08730 R14: ffff8880a0d086e8 R15: 0000000000000000
FS: 00007f14b09467a0(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000625208 CR3: 000000006128d000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__list_add include/linux/list.h:60 [inline]
list_add_tail include/linux/list.h:93 [inline]
ext4_es_list_add fs/ext4/extents_status.c:424 [inline]
ext4_es_alloc_extent fs/ext4/extents_status.c:461 [inline]
__es_insert_extent+0xc29/0xf20 fs/ext4/extents_status.c:788
ext4_es_insert_extent+0x2b7/0xa40 fs/ext4/extents_status.c:843
ext4_map_blocks+0x66c/0x18e0 fs/ext4/inode.c:583
ext4_getblk+0x40b/0x510 fs/ext4/inode.c:964
ext4_bread_batch+0x7f/0x420 fs/ext4/inode.c:1034
ext4_find_entry+0x7a3/0x1150 fs/ext4/namei.c:1426
ext4_lookup fs/ext4/namei.c:1558 [inline]
ext4_lookup+0x168/0x700 fs/ext4/namei.c:1544
lookup_open+0x6d4/0x1b10 fs/namei.c:3211
do_last fs/namei.c:3322 [inline]
path_openat+0x1eb4/0x46e0 fs/namei.c:3533
do_filp_open+0x1a1/0x280 fs/namei.c:3563
do_open_execat+0x137/0x690 fs/exec.c:856
__do_execve_file.isra.0+0x178d/0x23f0 fs/exec.c:1758
do_execveat_common fs/exec.c:1865 [inline]
do_execve fs/exec.c:1882 [inline]
__do_sys_execve fs/exec.c:1958 [inline]
__se_sys_execve fs/exec.c:1953 [inline]
__x64_sys_execve+0x8f/0xc0 fs/exec.c:1953
do_syscall_64+0x103/0x610 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f14b002a207
Code: 77 19 f4 48 89 d7 44 89 c0 0f 05 48 3d 00 f0 ff ff 76 e0 f7 d8 64 41
89 01 eb d8 f7 d8 64 41 89 01 eb df b8 3b 00 00 00 0f 05 <48> 3d 00 f0 ff
ff 77 02 f3 c3 48 8b 15 00 8c 2d 00 f7 d8 64 89 02
RSP: 002b:00007ffd29dcd118 EFLAGS: 00000206 ORIG_RAX: 000000000000003b
RAX: ffffffffffffffda RBX: 00000000ffffffff RCX: 00007f14b002a207
RDX: 0000000002536270 RSI: 00007ffd29dcd210 RDI: 00007ffd29dce220
RBP: 0000000000625500 R08: 000000000000271a R09: 000000000000271a
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000002536270
R13: 0000000000000007 R14: 0000000002525250 R15: 0000000000000005
Modules linked in:
---[ end trace 12e01f68d2ed9a83 ]---
RIP: 0010:__list_add_valid.cold+0x3a/0x3c lib/list_debug.c:26
Code: 0b 48 89 f2 4c 89 e1 4c 89 ee 48 c7 c7 c0 dc a1 87 e8 29 9c 29 fe 0f
0b 48 89 f1 48 c7 c7 40 dc a1 87 4c 89 e6 e8 15 9c 29 fe <0f> 0b 4c 89 f6
48 c7 c7 e0 dd a1 87 e8 04 9c 29 fe 0f 0b 4c 89 ea
RSP: 0018:ffff888055237110 EFLAGS: 00010286
RAX: 0000000000000075 RBX: ffff88821671c6c0 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff815b0096 RDI: ffffed100aa46e14
RBP: ffff888055237128 R08: 0000000000000075 R09: ffffed1015d25011
R10: ffffed1015d25010 R11: ffff8880ae928087 R12: ffff88821671cc90
R13: ffff8880a0d08730 R14: ffff8880a0d086e8 R15: 0000000000000000
FS: 00007f14b09467a0(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000625208 CR3: 000000006128d000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.

syzbot

unread,
Sep 5, 2019, 3:50:04 PM9/5/19
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages