BUG: unable to handle kernel paging request in free_block

18 views
Skip to first unread message

syzbot

unread,
Jul 20, 2020, 11:09:25 PM7/20/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 17a87580 Linux 4.19.133
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=151db27f100000
kernel config: https://syzkaller.appspot.com/x/.config?x=562879a87122f7ce
dashboard link: https://syzkaller.appspot.com/bug?extid=aa8165e574f7da5a0f90
compiler: gcc (GCC) 10.1.0-syz 20200507

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+aa8165...@syzkaller.appspotmail.com

netlink: 12 bytes leftover after parsing attributes in process `syz-executor.3'.
BUG: unable to handle kernel paging request at ffffffff00000101
PGD 8c70067 P4D 8c70067 PUD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 24796 Comm: kworker/0:5 Not tainted 4.19.133-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
IPVS: Unknown mcast interface: rose0
Workqueue: events cache_reap
RIP: 0010:__list_del_entry_valid+0x87/0xef lib/list_debug.c:51
Code: 48 b8 00 02 00 00 00 00 ad de 49 39 c4 0f 84 e0 00 00 00 48 b8 00 00 00 00 00 fc ff df 4c 89 e2 48 c1 ea 03 80 3c 02 00 75 51 <49> 8b 14 24 48 39 ea 0f 85 97 00 00 00 49 8d 7d 08 48 b8 00 00 00
RSP: 0018:ffff888214b07c08 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffffe8ffffc11488 RCX: ffffffffffffffff
RDX: 1fffffffe0000020 RSI: ffffffff8130ec6a RDI: ffffea0000004550
RBP: ffffea0000004548 R08: 0000000000004540 R09: 0000000000000000
R10: 0000000000000007 R11: 0000000000000000 R12: ffffffff00000101
R13: 0000000000000000 R14: ffffea0000004540 R15: ffff8880a6718000
FS: 0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffff00000101 CR3: 0000000094422000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__list_del_entry include/linux/list.h:117 [inline]
list_del include/linux/list.h:125 [inline]
free_block+0xd3/0x230 mm/slab.c:3421
drain_array_locked+0x30/0x80 mm/slab.c:2213
drain_array+0x80/0xa0 mm/slab.c:4027
cache_reap+0x150/0x270 mm/slab.c:4068
process_one_work+0x864/0x1570 kernel/workqueue.c:2155
worker_thread+0x64c/0x1130 kernel/workqueue.c:2298
kthread+0x30b/0x410 kernel/kthread.c:246
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Modules linked in:
CR2: ffffffff00000101
---[ end trace 22d253f6a885d5ce ]---
RIP: 0010:__list_del_entry_valid+0x87/0xef lib/list_debug.c:51
Code: 48 b8 00 02 00 00 00 00 ad de 49 39 c4 0f 84 e0 00 00 00 48 b8 00 00 00 00 00 fc ff df 4c 89 e2 48 c1 ea 03 80 3c 02 00 75 51 <49> 8b 14 24 48 39 ea 0f 85 97 00 00 00 49 8d 7d 08 48 b8 00 00 00
RSP: 0018:ffff888214b07c08 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffffe8ffffc11488 RCX: ffffffffffffffff
RDX: 1fffffffe0000020 RSI: ffffffff8130ec6a RDI: ffffea0000004550
RBP: ffffea0000004548 R08: 0000000000004540 R09: 0000000000000000
R10: 0000000000000007 R11: 0000000000000000 R12: ffffffff00000101
R13: 0000000000000000 R14: ffffea0000004540 R15: ffff8880a6718000
FS: 0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffff00000101 CR3: 0000000094422000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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

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

syzbot

unread,
Nov 17, 2020, 10:09:23 PM11/17/20
to syzkaller...@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