Hello,
syzbot found the following crash on:
HEAD commit: e1243231 ANDROID: ufs, block: fix crypto power management ..
git tree: android-5.4
console output:
https://syzkaller.appspot.com/x/log.txt?x=17839de9e00000
kernel config:
https://syzkaller.appspot.com/x/.config?x=79f4207b7df25c17
dashboard link:
https://syzkaller.appspot.com/bug?extid=ef9efc0b646a3369800c
compiler: Android (6032204 based on r370808) clang version 10.0.1 (
https://android.googlesource.com/toolchain/llvm-project 6e765c10313d15c02ab29977a82938f66742c3a9)
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=147be27ee00000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=1311a779e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by:
syzbot+ef9efc...@syzkaller.appspotmail.com
audit: audit_backlog=23 > audit_backlog_limit=7
audit: audit_lost=1 audit_rate_limit=0 audit_backlog_limit=7
Kernel panic - not syncing: audit: backlog limit exceeded
CPU: 1 PID: 1891 Comm: syz-executor837 Not tainted 5.4.21-syzkaller-00756-ge12432318607 #0
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+0x1b0/0x228 lib/dump_stack.c:118
panic+0x26c/0x719 kernel/panic.c:221
audit_panic kernel/audit.c:306 [inline]
audit_log_lost+0x1d7/0x1e0 kernel/audit.c:376
audit_log_start+0x55b/0x9a0 kernel/audit.c:1795
audit_log+0x99/0x130 kernel/audit.c:2343
xt_replace_table+0x61b/0x7a0 net/netfilter/x_tables.c:1413
xt_register_table+0x238/0x590 net/netfilter/x_tables.c:1452
arpt_register_table+0x161/0x6d0 net/ipv4/netfilter/arp_tables.c:1559
arptable_filter_table_init+0x7b/0xa0 net/ipv4/netfilter/arptable_filter.c:53
xt_find_table_lock+0x251/0x3a0 net/netfilter/x_tables.c:1223
xt_request_find_table_lock+0x27/0xc0 net/netfilter/x_tables.c:1253
get_info+0x1c3/0x530 net/ipv4/netfilter/arp_tables.c:808
do_arpt_get_ctl+0x151/0x9a0 net/ipv4/netfilter/arp_tables.c:1485
nf_sockopt net/netfilter/nf_sockopt.c:104 [inline]
nf_getsockopt+0x28e/0x2b0 net/netfilter/nf_sockopt.c:122
ip_getsockopt+0x13c/0x230 net/ipv4/ip_sockglue.c:1576
tcp_getsockopt+0xbe/0xd0 net/ipv4/tcp.c:3691
sock_common_getsockopt+0x99/0xb0 net/core/sock.c:3110
__sys_getsockopt+0x1f4/0x360 net/socket.c:2130
__do_sys_getsockopt net/socket.c:2145 [inline]
__se_sys_getsockopt net/socket.c:2142 [inline]
__x64_sys_getsockopt+0xbf/0xd0 net/socket.c:2142
do_syscall_64+0xc0/0x100 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x44494a
Code: b8 10 01 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 8d df fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 37 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 6a df fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:00007ffe7e51b1b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000037
RAX: ffffffffffffffda RBX: 00000000004a31c9 RCX: 000000000044494a
RDX: 0000000000000060 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 0000000000000003 R08: 00007ffe7e51b1cc R09: 0000000000000000
R10: 00000000006cd448 R11: 0000000000000246 R12: 00000000006ccdc8
R13: 0000000000402dd0 R14: 0000000000000000 R15: 0000000000000000
Shutting down cpus with NMI
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
syzk...@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches