lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 26 May 2018 02:14:02 -0700 From: syzbot <syzbot+9e762b52dd17e616a7a5@...kaller.appspotmail.com> To: ast@...nel.org, daniel@...earbox.net, davem@...emloft.net, hpa@...or.com, kuznet@....inr.ac.ru, linux-kernel@...r.kernel.org, mingo@...hat.com, netdev@...r.kernel.org, syzkaller-bugs@...glegroups.com, tglx@...utronix.de, x86@...nel.org, yoshfuji@...ux-ipv6.org Subject: WARNING in bpf_int_jit_compile Hello, syzbot found the following crash on: HEAD commit: 203ec2fed17a Merge tag 'armsoc-fixes' of git://git.kernel... git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=14f0d5a7800000 kernel config: https://syzkaller.appspot.com/x/.config?x=f3b4e30da84ec1ed dashboard link: https://syzkaller.appspot.com/bug?extid=9e762b52dd17e616a7a5 compiler: gcc (GCC) 8.0.1 20180413 (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+9e762b52dd17e616a7a5@...kaller.appspotmail.com RAX: ffffffffffffffda RBX: 00007f9da107d6d4 RCX: 0000000000455a09 RDX: 0000000000000048 RSI: 000000002000e000 RDI: 0000000000000005 RBP: 000000000072bea0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000014 R13: 0000000000000046 R14: 00000000006f4730 R15: 0000000000000021 WARNING: CPU: 0 PID: 20757 at include/linux/filter.h:667 bpf_jit_binary_lock_ro include/linux/filter.h:667 [inline] WARNING: CPU: 0 PID: 20757 at include/linux/filter.h:667 bpf_int_jit_compile+0xbf7/0xef7 arch/x86/net/bpf_jit_comp.c:1271 Kernel panic - not syncing: panic_on_warn set ... CPU: 0 PID: 20757 Comm: syz-executor6 Not tainted 4.17.0-rc5+ #60 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+0x1b9/0x294 lib/dump_stack.c:113 panic+0x22f/0x4de kernel/panic.c:184 __warn.cold.8+0x163/0x1b3 kernel/panic.c:536 report_bug+0x252/0x2d0 lib/bug.c:186 fixup_bug arch/x86/kernel/traps.c:178 [inline] do_error_trap+0x1de/0x490 arch/x86/kernel/traps.c:296 do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:315 invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:992 RIP: 0010:bpf_jit_binary_lock_ro include/linux/filter.h:667 [inline] RIP: 0010:bpf_int_jit_compile+0xbf7/0xef7 arch/x86/net/bpf_jit_comp.c:1271 RSP: 0018:ffff8801b3fbf920 EFLAGS: 00010246 RAX: 0000000000040000 RBX: 0000000000000047 RCX: ffffc900050da000 RDX: 0000000000040000 RSI: ffffffff81444d37 RDI: 0000000000000005 RBP: ffff8801b3fbfa40 R08: ffff8801b4c18040 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90001932002 R13: ffff8801b3fbfa18 R14: 00000000fffffff4 R15: 0000000000000003 bpf_prog_select_runtime+0x131/0x640 kernel/bpf/core.c:1491 bpf_prog_load+0x16c2/0x2070 kernel/bpf/syscall.c:1333 __do_sys_bpf kernel/bpf/syscall.c:2073 [inline] __se_sys_bpf kernel/bpf/syscall.c:2035 [inline] __x64_sys_bpf+0x389/0x4c0 kernel/bpf/syscall.c:2035 do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x455a09 RSP: 002b:00007f9da107cc68 EFLAGS: 00000246 ORIG_RAX: 0000000000000141 RAX: ffffffffffffffda RBX: 00007f9da107d6d4 RCX: 0000000000455a09 RDX: 0000000000000048 RSI: 000000002000e000 RDI: 0000000000000005 RBP: 000000000072bea0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000014 R13: 0000000000000046 R14: 00000000006f4730 R15: 0000000000000021 Dumping ftrace buffer: (ftrace buffer empty) 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 syzkaller@...glegroups.com. syzbot will keep track of this bug report. See: https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with syzbot.
Powered by blists - more mailing lists