general protection fault in __purge_vmap_area_lazy

43 views
Skip to first unread message

syzbot

unread,
Sep 23, 2020, 10:16:22 AM9/23/20
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: eb5f95f1 Merge tag 's390-5.9-6' of git://git.kernel.org/pu..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11d08ec5900000
kernel config: https://syzkaller.appspot.com/x/.config?x=ffe85b197a57c180
dashboard link: https://syzkaller.appspot.com/bug?extid=9ab6d1226af17c126e08
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [b...@alien8.de dave....@linux.intel.com h...@zytor.com linux-...@vger.kernel.org lu...@kernel.org mi...@redhat.com pet...@infradead.org tg...@linutronix.de x...@kernel.org]

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

general protection fault, probably for non-canonical address 0xe0edfcedfffffff9: 0000 [#1] PREEMPT SMP KASAN
KASAN: maybe wild-memory-access in range [0x0770076fffffffc8-0x0770076fffffffcf]
CPU: 1 PID: 10596 Comm: syz-executor.4 Not tainted 5.9.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__purge_vmap_area_lazy+0xb5/0x1b70 mm/vmalloc.c:1346
Code: 48 8d 43 c8 48 85 db 48 89 04 24 0f 84 d3 11 00 00 49 bd 00 00 00 00 00 fc ff df 48 89 c3 e8 92 ff c9 ff 48 89 d8 48 c1 e8 03 <42> 80 3c 28 00 0f 85 04 17 00 00 48 8b 03 48 8d 7b 08 48 39 c5 48
RSP: 0018:ffffc90008e97870 EFLAGS: 00010206
RAX: 00ee00edfffffff9 RBX: 0770076fffffffc8 RCX: ffffc90011548000
RDX: 0000000000040000 RSI: ffffffff81ac402e RDI: ffff888000108b78
RBP: 0000007700000770 R08: 0000000000000001 R09: ffffffff8d1bc687
R10: fffffbfff1a378d0 R11: 0000000000000000 R12: ffffc90009575000
R13: dffffc0000000000 R14: 0000000000000007 R15: 0000000000000002
FS: 00007f395f4cf700(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b31f30000 CR3: 00000000959d7000 CR4: 00000000001526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
_vm_unmap_aliases.part.0+0x3d6/0x4e0 mm/vmalloc.c:1770
_vm_unmap_aliases mm/vmalloc.c:1744 [inline]
vm_unmap_aliases+0x42/0x50 mm/vmalloc.c:1793
change_page_attr_set_clr+0x241/0x500 arch/x86/mm/pat/set_memory.c:1732
change_page_attr_clear arch/x86/mm/pat/set_memory.c:1789 [inline]
set_memory_ro+0x78/0xa0 arch/x86/mm/pat/set_memory.c:1935
bpf_jit_binary_lock_ro include/linux/filter.h:815 [inline]
bpf_int_jit_compile+0xd96/0x111e arch/x86/net/bpf_jit_comp.c:1929
bpf_prog_select_runtime+0x59b/0xb20 kernel/bpf/core.c:1807
bpf_migrate_filter+0x2dc/0x380 net/core/filter.c:1290
bpf_prepare_filter net/core/filter.c:1338 [inline]
bpf_prog_create_from_user+0x51b/0x660 net/core/filter.c:1432
seccomp_prepare_filter kernel/seccomp.c:567 [inline]
seccomp_prepare_user_filter kernel/seccomp.c:604 [inline]
seccomp_set_mode_filter kernel/seccomp.c:1546 [inline]
do_seccomp+0x7ba/0x2540 kernel/seccomp.c:1661
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45d5f9
Code: 5d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 2b b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f395f4cec78 EFLAGS: 00000246 ORIG_RAX: 000000000000013d
RAX: ffffffffffffffda RBX: 00000000000274c0 RCX: 000000000045d5f9
RDX: 00000000200000c0 RSI: 0000000000000000 RDI: 0000000000000001
RBP: 000000000118d020 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cfec
R13: 000000000169fb6f R14: 00007f395f4cf9c0 R15: 000000000118cfec
Modules linked in:
---[ end trace 826514556da3daca ]---
RIP: 0010:__purge_vmap_area_lazy+0xb5/0x1b70 mm/vmalloc.c:1346
Code: 48 8d 43 c8 48 85 db 48 89 04 24 0f 84 d3 11 00 00 49 bd 00 00 00 00 00 fc ff df 48 89 c3 e8 92 ff c9 ff 48 89 d8 48 c1 e8 03 <42> 80 3c 28 00 0f 85 04 17 00 00 48 8b 03 48 8d 7b 08 48 39 c5 48
RSP: 0018:ffffc90008e97870 EFLAGS: 00010206
RAX: 00ee00edfffffff9 RBX: 0770076fffffffc8 RCX: ffffc90011548000
RDX: 0000000000040000 RSI: ffffffff81ac402e RDI: ffff888000108b78
RBP: 0000007700000770 R08: 0000000000000001 R09: ffffffff8d1bc687
R10: fffffbfff1a378d0 R11: 0000000000000000 R12: ffffc90009575000
R13: dffffc0000000000 R14: 0000000000000007 R15: 0000000000000002
FS: 00007f395f4cf700(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000747698 CR3: 00000000959d7000 CR4: 00000000001526f0
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,
Dec 18, 2020, 9:12:07 AM12/18/20
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