syzbot


suspicious RCU usage at ./include/linux/rcupdate.h:LINE

Status: closed as invalid on 2017/08/27 08:48
First crash: 2484d, last: 2484d
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream suspicious RCU usage at ./include/linux/rcupdate.h:LINE (2) net C 174 2337d 2416d 4/27 fixed on 2018/01/22 13:19
upstream suspicious RCU usage at ./include/linux/rcupdate.h:LINE (4) perf C 7264 2321d 2324d 4/27 fixed on 2018/02/12 17:26
upstream suspicious RCU usage at ./include/linux/rcupdate.h:LINE (3) bpf C 5087 2327d 2336d 4/27 fixed on 2018/02/01 04:00

Sample crash report:

=============================
WARNING: suspicious RCU usage
4.13.0-rc6-next-20170825+ #9 Not tainted
-----------------------------
./include/linux/rcupdate.h:302 Illegal context switch in RCU read-side critical section!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 0
6 locks held by syz-executor4/3063:
 #0:  (&dup_mmap_sem){.+.+}, at: [<ffffffff813f9968>] dup_mmap kernel/fork.c:603 [inline]
 #0:  (&dup_mmap_sem){.+.+}, at: [<ffffffff813f9968>] dup_mm kernel/fork.c:1171 [inline]
 #0:  (&dup_mmap_sem){.+.+}, at: [<ffffffff813f9968>] copy_mm+0x3c6/0x1310 kernel/fork.c:1225
 #1:  (&mm->mmap_sem){++++}, at: [<ffffffff813f9984>] dup_mmap kernel/fork.c:604 [inline]
 #1:  (&mm->mmap_sem){++++}, at: [<ffffffff813f9984>] dup_mm kernel/fork.c:1171 [inline]
 #1:  (&mm->mmap_sem){++++}, at: [<ffffffff813f9984>] copy_mm+0x3e2/0x1310 kernel/fork.c:1225
 #2:  (&mm->mmap_sem/1){+.+.}, at: [<ffffffff813f99e1>] dup_mmap kernel/fork.c:613 [inline]
 #2:  (&mm->mmap_sem/1){+.+.}, at: [<ffffffff813f99e1>] dup_mm kernel/fork.c:1171 [inline]
 #2:  (&mm->mmap_sem/1){+.+.}, at: [<ffffffff813f99e1>] copy_mm+0x43f/0x1310 kernel/fork.c:1225
 #3:  (rcu_read_lock){....}, at: [<ffffffff83e93603>] arch_static_branch arch/x86/include/asm/jump_label.h:35 [inline]
 #3:  (rcu_read_lock){....}, at: [<ffffffff83e93603>] static_key_false include/linux/jump_label.h:141 [inline]
 #3:  (rcu_read_lock){....}, at: [<ffffffff83e93603>] netif_receive_skb_internal+0x93/0x5e0 net/core/dev.c:4498
 #4:  (rcu_read_lock){....}, at: [<ffffffff8405af49>] __skb_pull include/linux/skbuff.h:2081 [inline]
 #4:  (rcu_read_lock){....}, at: [<ffffffff8405af49>] ip_local_deliver_finish+0x179/0xba0 net/ipv4/ip_input.c:194
 #5:  (slock-AF_INET/1){+.-.}, at: [<ffffffff841185d2>] tcp_v4_rcv+0x2312/0x2f20 net/ipv4/tcp_ipv4.c:1716

stack backtrace:
CPU: 0 PID: 3063 Comm: syz-executor4 Not tainted 4.13.0-rc6-next-20170825+ #9
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:16 [inline]
 dump_stack+0x194/0x257 lib/dump_stack.c:52
 lockdep_rcu_suspicious+0x123/0x170 kernel/locking/lockdep.c:4678
 rcu_preempt_sleep_check include/linux/rcupdate.h:301 [inline]
 ___might_sleep+0x385/0x470 kernel/sched/core.c:5987
 __might_sleep+0x95/0x190 kernel/sched/core.c:5975
 down_write+0x67/0x120 kernel/locking/rwsem.c:52
 i_mmap_lock_write include/linux/fs.h:467 [inline]
 dup_mmap kernel/fork.c:678 [inline]
 dup_mm kernel/fork.c:1171 [inline]
 copy_mm+0xbf7/0x1310 kernel/fork.c:1225
 copy_process.part.35+0x1eae/0x4af0 kernel/fork.c:1727
 copy_process kernel/fork.c:1540 [inline]
 _do_fork+0x1ef/0xfe0 kernel/fork.c:2019
 SYSC_clone kernel/fork.c:2129 [inline]
 SyS_clone+0x37/0x50 kernel/fork.c:2123
 do_syscall_64+0x26c/0x8c0 arch/x86/entry/common.c:287
 entry_SYSCALL64_slow_path+0x25/0x25
RIP: 0033:0x444d94
RSP: 002b:0000000000a5f9a0 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 0000000000444d94
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
RBP: 0000000000a5fa00 R08: 0000000000000001 R09: 0000000001cb0940
R10: 0000000001cb0c10 R11: 0000000000000246 R12: 0000000000a5f9a0
R13: 0000000000a5f9c0 R14: 000000000000001c R15: 0000000000008d2d
======================================================
WARNING: possible circular locking dependency detected
4.13.0-rc6-next-20170825+ #9 Not tainted
------------------------------------------------------
kworker/2:3/3782 is trying to acquire lock:
 ((&(&ifa->dad_work)->work)){+.+.}, at: [<ffffffff8146858c>] process_one_work+0xb2c/0x1be0 kernel/workqueue.c:2094

but now in release context of a crosslock acquired at the following:
 ((complete)&rcu.completion){+.+.}, at: [<ffffffff815b4075>] __synchronize_srcu+0x1b5/0x250 kernel/rcu/srcutree.c:898

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 ((complete)&rcu.completion){+.+.}:
       check_prevs_add kernel/locking/lockdep.c:2020 [inline]
       validate_chain kernel/locking/lockdep.c:2469 [inline]
       __lock_acquire+0x3286/0x4620 kernel/locking/lockdep.c:3498
       lock_acquire+0x1d5/0x580 kernel/locking/lockdep.c:4002
       complete_acquire include/linux/completion.h:39 [inline]
       __wait_for_common kernel/sched/completion.c:108 [inline]
       wait_for_common kernel/sched/completion.c:122 [inline]
       wait_for_completion+0xc8/0x770 kernel/sched/completion.c:143
       __synchronize_srcu+0x1b5/0x250 kernel/rcu/srcutree.c:898
       synchronize_srcu_expedited kernel/rcu/srcutree.c:923 [inline]
       synchronize_srcu+0x1a3/0x560 kernel/rcu/srcutree.c:974
       quarantine_remove_cache+0xd7/0xf0 mm/kasan/quarantine.c:327
       kasan_cache_shrink+0x9/0x10 mm/kasan/kasan.c:380
       kmem_cache_shrink+0x15/0x30 mm/slab_common.c:857
       acpi_os_purge_cache+0x15/0x20 drivers/acpi/osl.c:1560
       acpi_purge_cached_objects+0x38/0xc9 drivers/acpi/acpica/utxface.c:271
       acpi_initialize_objects+0xc5/0x112 drivers/acpi/acpica/utxfinit.c:302
       acpi_bus_init drivers/acpi/bus.c:1131 [inline]
       acpi_init+0x23c/0x8e6 drivers/acpi/bus.c:1220
       do_one_initcall+0x9e/0x330 init/main.c:826
       do_initcall_level init/main.c:892 [inline]
       do_initcalls init/main.c:900 [inline]
       do_basic_setup init/main.c:918 [inline]
       kernel_init_freeable+0x469/0x521 init/main.c:1066
       kernel_init+0x13/0x172 init/main.c:993
       ret_from_fork+0x2a/0x40 arch/x86/entry/entry_64.S:431

-> #2 (cpu_hotplug_lock.rw_sem){++++}:
       check_prevs_add kernel/locking/lockdep.c:2020 [inline]
       validate_chain kernel/locking/lockdep.c:2469 [inline]
       __lock_acquire+0x3286/0x4620 kernel/locking/lockdep.c:3498
       lock_acquire+0x1d5/0x580 kernel/locking/lockdep.c:4002
       percpu_down_read_preempt_disable include/linux/percpu-rwsem.h:35 [inline]
       percpu_down_read include/linux/percpu-rwsem.h:58 [inline]
       cpus_read_lock+0x42/0x90 kernel/cpu.c:218
       get_online_cpus include/linux/cpu.h:126 [inline]
       flush_all_backlogs net/core/dev.c:4592 [inline]
       rollback_registered_many+0x587/0xe80 net/core/dev.c:7127
       rollback_registered+0x1be/0x3c0 net/core/dev.c:7183
       unregister_netdevice_queue+0x2e3/0x5d0 net/core/dev.c:8171
       unregister_netdevice include/linux/netdevice.h:2428 [inline]
       __tun_detach+0x1020/0x1390 drivers/net/tun.c:576
       tun_detach drivers/net/tun.c:587 [inline]
       tun_chr_close+0x44/0x60 drivers/net/tun.c:2595
       __fput+0x333/0x7f0 fs/file_table.c:210
       ____fput+0x15/0x20 fs/file_table.c:246
       task_work_run+0x199/0x270 kernel/task_work.c:112
       exit_task_work include/linux/task_work.h:21 [inline]
       do_exit+0xa52/0x1b40 kernel/exit.c:865
       do_group_exit+0x149/0x400 kernel/exit.c:968
       get_signal+0x7e8/0x17e0 kernel/signal.c:2334
       do_signal+0x94/0x1ee0 arch/x86/kernel/signal.c:808
       exit_to_usermode_loop+0x224/0x300 arch/x86/entry/common.c:158
       prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline]
       syscall_return_slowpath+0x42f/0x500 arch/x86/entry/common.c:266
       entry_SYSCALL_64_fastpath+0xbc/0xbe

-> #1 (rtnl_mutex){+.+.}:
       check_prevs_add kernel/locking/lockdep.c:2020 [inline]
       validate_chain kernel/locking/lockdep.c:2469 [inline]
       __lock_acquire+0x3286/0x4620 kernel/locking/lockdep.c:3498
       lock_acquire+0x1d5/0x580 kernel/locking/lockdep.c:4002
       __mutex_lock_common kernel/locking/mutex.c:756 [inline]
       __mutex_lock+0x16f/0x1870 kernel/locking/mutex.c:893
       mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:908
       rtnl_lock+0x17/0x20 net/core/rtnetlink.c:72
       addrconf_dad_work+0xbb/0xfc0 net/ipv6/addrconf.c:3890
       process_one_work+0xbfd/0x1be0 kernel/workqueue.c:2098
       worker_thread+0x223/0x1860 kernel/workqueue.c:2233
       kthread+0x39c/0x470 kernel/kthread.c:231
       ret_from_fork+0x2a/0x40 arch/x86/entry/entry_64.S:431

-> #0 ((&(&ifa->dad_work)->work)){+.+.}:
       process_one_work+0xba5/0x1be0 kernel/workqueue.c:2095
       worker_thread+0x223/0x1860 kernel/workqueue.c:2233
       kthread+0x39c/0x470 kernel/kthread.c:231
       ret_from_fork+0x2a/0x40 arch/x86/entry/entry_64.S:431
       0xffffffffffffffff

other info that might help us debug this:

Chain exists of:
  (&(&ifa->dad_work)->work) --> cpu_hotplug_lock.rw_sem --> (complete)&rcu.completion

 Possible unsafe locking scenario by crosslock:

       CPU0                    CPU1
       ----                    ----
  lock(cpu_hotplug_lock.rw_sem);
  lock((complete)&rcu.completion);
                               lock((&(&ifa->dad_work)->work));
                               unlock((complete)&rcu.completion);

 *** DEADLOCK ***

3 locks held by kworker/2:3/3782:
 #0:  ("events_power_efficient"){.+.+}, at: [<ffffffff81468534>] __write_once_size include/linux/compiler.h:305 [inline]
 #0:  ("events_power_efficient"){.+.+}, at: [<ffffffff81468534>] atomic64_set arch/x86/include/asm/atomic64_64.h:33 [inline]
 #0:  ("events_power_efficient"){.+.+}, at: [<ffffffff81468534>] atomic_long_set include/asm-generic/atomic-long.h:56 [inline]
 #0:  ("events_power_efficient"){.+.+}, at: [<ffffffff81468534>] set_work_data kernel/workqueue.c:617 [inline]
 #0:  ("events_power_efficient"){.+.+}, at: [<ffffffff81468534>] set_work_pool_and_clear_pending kernel/workqueue.c:644 [inline]
 #0:  ("events_power_efficient"){.+.+}, at: [<ffffffff81468534>] process_one_work+0xad4/0x1be0 kernel/workqueue.c:2090
 #1:  ((&(&sdp->work)->work)){+.+.}, at: [<ffffffff8146858c>] process_one_work+0xb2c/0x1be0 kernel/workqueue.c:2094
 #2:  (&x->wait#5){....}, at: [<ffffffff81528c68>] complete+0x18/0x80 kernel/sched/completion.c:34

stack backtrace:
CPU: 2 PID: 3782 Comm: kworker/2:3 Not tainted 4.13.0-rc6-next-20170825+ #9
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
Workqueue: events_power_efficient srcu_invoke_callbacks
Call Trace:
 __dump_stack lib/dump_stack.c:16 [inline]
 dump_stack+0x194/0x257 lib/dump_stack.c:52
 print_circular_bug+0x503/0x710 kernel/locking/lockdep.c:1259
 check_prev_add+0x865/0x1520 kernel/locking/lockdep.c:1894
 commit_xhlock kernel/locking/lockdep.c:5002 [inline]
 commit_xhlocks kernel/locking/lockdep.c:5046 [inline]
 lock_commit_crosslock+0xe73/0x1d10 kernel/locking/lockdep.c:5085
 complete_release_commit include/linux/completion.h:49 [inline]
 complete+0x24/0x80 kernel/sched/completion.c:39
 wakeme_after_rcu+0xd/0x10 kernel/rcu/update.c:376
 srcu_invoke_callbacks+0x280/0x4d0 kernel/rcu/srcutree.c:1161
 process_one_work+0xbfd/0x1be0 kernel/workqueue.c:2098
 worker_thread+0x223/0x1860 kernel/workqueue.c:2233
 kthread+0x39c/0x470 kernel/kthread.c:231
 ret_from_fork+0x2a/0x40 arch/x86/entry/entry_64.S:431
TCP: request_sock_TCP: Possible SYN flooding on port 20024. Sending cookies.  Check SNMP counters.
device lo entered promiscuous mode
kvm [6073]: vcpu0, guest rIP: 0x9135 Hyper-V unhandled rdmsr: 0x4000008f
kvm [6073]: vcpu0, guest rIP: 0x9135 Hyper-V unhandled rdmsr: 0x4000008e
kvm [6073]: vcpu0, guest rIP: 0x9135 Hyper-V unhandled rdmsr: 0x4000008d
kvm [6073]: vcpu0, guest rIP: 0x9135 Hyper-V unhandled rdmsr: 0x4000008c
kvm [6073]: vcpu0, guest rIP: 0x9135 Hyper-V unhandled rdmsr: 0x4000008b
kvm [6073]: vcpu0, guest rIP: 0x9135 Hyper-V unhandled rdmsr: 0x4000008a
kvm [6073]: vcpu0, guest rIP: 0x9135 Hyper-V unhandled rdmsr: 0x40000089
kvm [6073]: vcpu0, guest rIP: 0x9135 Hyper-V unhandled rdmsr: 0x40000088
kvm [6073]: vcpu0, guest rIP: 0x9135 Hyper-V unhandled rdmsr: 0x40000087
kvm [6073]: vcpu0, guest rIP: 0x9135 Hyper-V unhandled rdmsr: 0x40000086
kvm [6073]: vcpu0, guest rIP: 0x9112 Hyper-V uhandled wrmsr: 0x40000023 data 0x66c900003b9a1043
kvm [6073]: vcpu0, guest rIP: 0x9112 Hyper-V uhandled wrmsr: 0x40000022 data 0x66c90000cb211043
kvm [6073]: vcpu0, guest rIP: 0x9112 Hyper-V uhandled wrmsr: 0x40000020 data 0x66c9000000061043
capability: warning: `syz-executor1' uses deprecated v2 capabilities in a way that may be insecure
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
net_ratelimit: 2 callbacks suppressed
sock: sock_set_timeout: `syz-executor5' (pid 6142) tries to set negative timeout
sctp: [Deprecated]: syz-executor6 (pid 6158) Use of int in maxseg socket option.
Use struct sctp_assoc_value instead
sctp: [Deprecated]: syz-executor6 (pid 6158) Use of struct sctp_assoc_value in delayed_ack socket option.
Use struct sctp_sack_info instead
sctp: [Deprecated]: syz-executor6 (pid 6158) Use of int in maxseg socket option.
Use struct sctp_assoc_value instead
sctp: [Deprecated]: syz-executor6 (pid 6161) Use of struct sctp_assoc_value in delayed_ack socket option.
Use struct sctp_sack_info instead
sock: sock_set_timeout: `syz-executor5' (pid 6142) tries to set negative timeout
QAT: Invalid ioctl
QAT: Invalid ioctl
device syz2 entered promiscuous mode
sctp: [Deprecated]: syz-executor1 (pid 6278) Use of struct sctp_assoc_value in delayed_ack socket option.
Use struct sctp_sack_info instead
device syz2 left promiscuous mode
device syz2 entered promiscuous mode
sctp: [Deprecated]: syz-executor1 (pid 6309) Use of struct sctp_assoc_value in delayed_ack socket option.
Use struct sctp_sack_info instead
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pig=6349 comm=syz-executor6
SELinux: unrecognized netlink message: protocol=4 nlmsg_type=82 sclass=netlink_tcpdiag_socket pig=6396 comm=syz-executor2
SELinux: unrecognized netlink message: protocol=4 nlmsg_type=82 sclass=netlink_tcpdiag_socket pig=6408 comm=syz-executor2
nla_parse: 20 callbacks suppressed
netlink: 1 bytes leftover after parsing attributes in process `syz-executor1'.
netlink: 1 bytes leftover after parsing attributes in process `syz-executor1'.
device lo entered promiscuous mode
device lo left promiscuous mode
device lo entered promiscuous mode
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pig=6610 comm=syz-executor2
device lo left promiscuous mode
QAT: Invalid ioctl
QAT: Invalid ioctl
device syz2 left promiscuous mode
skbuff: bad partial csum: csum=65285/255 len=14
ALSA: seq fatal error: cannot create timer (-22)
sctp: [Deprecated]: syz-executor7 (pid 6753) Use of struct sctp_assoc_value in delayed_ack socket option.
Use struct sctp_sack_info instead
sctp: [Deprecated]: syz-executor7 (pid 6753) Use of struct sctp_assoc_value in delayed_ack socket option.
Use struct sctp_sack_info instead
device syz5 entered promiscuous mode
netlink: 1 bytes leftover after parsing attributes in process `syz-executor5'.
netlink: 1 bytes leftover after parsing attributes in process `syz-executor5'.
QAT: Invalid ioctl
TCP: request_sock_TCP: Possible SYN flooding on port 20028. Sending cookies.  Check SNMP counters.
SELinux: unrecognized netlink message: protocol=9 nlmsg_type=0 sclass=netlink_audit_socket pig=7060 comm=syz-executor4
SELinux: unrecognized netlink message: protocol=9 nlmsg_type=0 sclass=netlink_audit_socket pig=7069 comm=syz-executor4
SELinux: unrecognized netlink message: protocol=6 nlmsg_type=65535 sclass=netlink_xfrm_socket pig=7122 comm=syz-executor7
netlink: 24 bytes leftover after parsing attributes in process `syz-executor7'.
netlink: 60 bytes leftover after parsing attributes in process `syz-executor7'.
netlink: 4052 bytes leftover after parsing attributes in process `syz-executor7'.
SELinux: unrecognized netlink message: protocol=6 nlmsg_type=65535 sclass=netlink_xfrm_socket pig=7151 comm=syz-executor7
netlink: 24 bytes leftover after parsing attributes in process `syz-executor7'.
netlink: 1 bytes leftover after parsing attributes in process `syz-executor4'.
device  entered promiscuous mode
netlink: 1 bytes leftover after parsing attributes in process `syz-executor4'.
device  left promiscuous mode
kauditd_printk_skb: 10 callbacks suppressed
audit: type=1326 audit(1503790811.985:1384): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=7262 comm="syz-executor3" exe="/syz-executor3" sig=31 arch=c000003e syscall=202 compat=0 ip=0x446749 code=0x0
QAT: Invalid ioctl
QAT: Invalid ioctl
SELinux: failure in selinux_parse_skb(), unable to parse packet
audit: type=1326 audit(1503790812.043:1385): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=7262 comm="syz-executor3" exe="/syz-executor3" sig=31 arch=c000003e syscall=202 compat=0 ip=0x446749 code=0x0
audit: type=1326 audit(1503790812.239:1386): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=7410 comm="syz-executor4" exe="/syz-executor4" sig=31 arch=c000003e syscall=202 compat=0 ip=0x446749 code=0xffff0000
kvm [7439]: vcpu0, guest rIP: 0x910f Hyper-V uhandled wrmsr: 0x4000008f data 0x4000f1
kvm [7439]: vcpu0, guest rIP: 0x910f Hyper-V uhandled wrmsr: 0x4000008e data 0x4000f2
kvm [7439]: vcpu0, guest rIP: 0x910f Hyper-V uhandled wrmsr: 0x4000008d data 0x4000f3
kvm [7439]: vcpu0, guest rIP: 0x910f Hyper-V uhandled wrmsr: 0x4000008c data 0x4000f4
kvm [7439]: vcpu0, guest rIP: 0x910f Hyper-V uhandled wrmsr: 0x4000008b data 0x4000f5
kvm [7439]: vcpu0, guest rIP: 0x910f Hyper-V uhandled wrmsr: 0x4000008a data 0x4000f6
kvm [7439]: vcpu0, guest rIP: 0x910f Hyper-V uhandled wrmsr: 0x40000089 data 0x4000f7
kvm [7439]: vcpu0, guest rIP: 0x910f Hyper-V uhandled wrmsr: 0x40000088 data 0x4000f8
TCP: request_sock_TCPv6: Possible SYN flooding on port 20005. Sending cookies.  Check SNMP counters.
kvm [7439]: vcpu0, guest rIP: 0x910f Hyper-V uhandled wrmsr: 0x40000020 data 0x400160
audit: type=1326 audit(1503790812.302:1387): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=7410 comm="syz-executor4" exe="/syz-executor4" sig=31 arch=c000003e syscall=202 compat=0 ip=0x446749 code=0xffff0000
[drm:drm_mode_legacy_fb_format] *ERROR* bad bpp, assuming x8r8g8b8 pixel format
device lo entered promiscuous mode
[drm:drm_mode_legacy_fb_format] *ERROR* bad bpp, assuming x8r8g8b8 pixel format
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pig=7525 comm=syz-executor1
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pig=7525 comm=syz-executor1
rpcbind: RPC call returned error 22
rpcbind: RPC call returned error 22
kvm: pic: non byte read
kvm: pic: non byte write
kvm: pic: non byte write
kvm: pic: non byte write
kvm: pic: non byte write
kvm: pic: non byte write
kvm: pic: non byte write
kvm: pic: non byte write
kvm: pic: non byte write
kvm: pic: non byte write
kvm: pic: level sensitive irq not supported
kvm: pic: non byte write
kvm: pic: level sensitive irq not supported
kvm: pic: single mode not supported
kvm: pic: single mode not supported
kvm: pic: level sensitive irq not supported
kvm: pic: single mode not supported
kvm: pic: level sensitive irq not supported
kvm: pic: non byte read
kvm: pic: level sensitive irq not supported
kvm: pic: level sensitive irq not supported
kvm: pic: single mode not supported
kvm: pic: single mode not supported
kvm: pic: level sensitive irq not supported
PF_BRIDGE: RTM_NEWNEIGH with invalid address
kvm: pic: single mode not supported
kvm: pic: level sensitive irq not supported
sctp: [Deprecated]: syz-executor1 (pid 7704) Use of struct sctp_assoc_value in delayed_ack socket option.
Use struct sctp_sack_info instead
sctp: [Deprecated]: syz-executor1 (pid 7704) Use of struct sctp_assoc_value in delayed_ack socket option.
Use struct sctp_sack_info instead
PF_BRIDGE: RTM_NEWNEIGH with invalid address
sctp: [Deprecated]: syz-executor2 (pid 7737) Use of int in max_burst socket option.
Use struct sctp_assoc_value instead
sctp: [Deprecated]: syz-executor1 (pid 7704) Use of struct sctp_assoc_value in delayed_ack socket option.
Use struct sctp_sack_info instead
sctp: [Deprecated]: syz-executor1 (pid 7704) Use of struct sctp_assoc_value in delayed_ack socket option.
Use struct sctp_sack_info instead
sctp: [Deprecated]: syz-executor2 (pid 7737) Use of int in max_burst socket option.
Use struct sctp_assoc_value instead
*** Guest State ***
CR0: actual=0x0000000080000021, shadow=0x0000000080000001, gh_mask=fffffffffffffff7
CR4: actual=0x0000000000002060, shadow=0x0000000000002020, gh_mask=ffffffffffffe871
CR3 = 0x0000000000002000
PDPTR0 = 0x0000000011e57ed0  PDPTR1 = 0x0000000000000000
PDPTR2 = 0x0000000000000000  PDPTR3 = 0x0000000000000000
RSP = 0x0000000000000f80  RIP = 0x0000000000000000
RFLAGS=0x00000002         DR7 = 0x0000000000000400
Sysenter RSP=0000000000000f80 CS:RIP=0050:0000000000002810
CS:   sel=0x0030, attr=0x0409b, limit=0x000fffff, base=0x0000000000000000
DS:   sel=0x0038, attr=0x04093, limit=0x000fffff, base=0x0000000000000000
SS:   sel=0x0038, attr=0x04093, limit=0x000fffff, base=0x0000000000000000
ES:   sel=0x0038, attr=0x04093, limit=0x000fffff, base=0x0000000000000000
FS:   sel=0x0038, attr=0x04093, limit=0x000fffff, base=0x0000000000000000
GS:   sel=0x0038, attr=0x04093, limit=0x000fffff, base=0x0000000000000000
GDTR:                           limit=0x000007ff, base=0x0000000000001000
LDTR: sel=0x0008, attr=0x04082, limit=0x000007ff, base=0x0000000000001800
IDTR:                           limit=0x000001ff, base=0x0000000000003800
TR:   sel=0x0009, attr=0x10000, limit=0x00006001, base=0x0000000000005000
EFER =     0x0000000000001800  PAT = 0x0007040600070406
DebugCtl = 0x0000000000000000  DebugExceptions = 0x0000000000000000
BndCfgS = 0x0000000000000000
Interruptibility = 00000000  ActivityState = 00000000
*** Host State ***
RIP = 0xffffffff811b8fd7  RSP = 0xffff88003d34f4c8
CS=0010 SS=0018 DS=0000 ES=0000 FS=0000 GS=0000 TR=0040
FSBase=00007f74fcb20700 GSBase=ffff88006df00000 TRBase=ffff88006df23100
GDTBase=ffffffffff574000 IDTBase=ffffffffff57b000
CR0=0000000080050033 CR3=000000005ad7c000 CR4=00000000000026e0
Sysenter RSP=0000000000000000 CS:RIP=0010:ffffffff84da5a70
EFER = 0x0000000000000d01  PAT = 0x0007040600070406
*** Control State ***
PinBased=0000003f CPUBased=b6986dfe SecondaryExec=000000e2
EntryControls=0001d1ff ExitControls=00afefff
ExceptionBitmap=00060042 PFECmask=00000000 PFECmatch=00000000
VMEntry: intr_info=80000003 errcode=00000000 ilen=00000000
VMExit: intr_info=00000000 errcode=00000000 ilen=00000001
        reason=80000021 qualification=0000000000000000
IDTVectoring: info=00000000 errcode=00000000
TSC Offset = 0xffffffdd45f3c084
EPT pointer = 0x000000003cd8201e
Virtual processor ID = 0x0001
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
syz-executor4 (7859) used greatest stack depth: 15032 bytes left
lo: Invalid MTU -494141437 requested, hw min 0
lo: Invalid MTU -494141437 requested, hw min 0
lo: Invalid MTU -494141437 requested, hw min 0
lo: Invalid MTU -494141437 requested, hw min 0
rpcbind: RPC call returned error 22
rpcbind: RPC call returned error 22
audit: type=1326 audit(1503790813.382:1388): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=8120 comm="syz-executor0" exe="/syz-executor0" sig=31 arch=c000003e syscall=202 compat=0 ip=0x446749 code=0xffff0000
audit: type=1326 audit(1503790813.404:1389): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=8120 comm="syz-executor0" exe="/syz-executor0" sig=31 arch=c000003e syscall=35 compat=0 ip=0x470501 code=0xffff0000
sctp: [Deprecated]: syz-executor1 (pid 8160) Use of int in maxseg socket option.
Use struct sctp_assoc_value instead
sctp: [Deprecated]: syz-executor1 (pid 8186) Use of int in maxseg socket option.
Use struct sctp_assoc_value instead
mmap: syz-executor7 (8228): VmData 17285120 exceed data ulimit 4. Update limits or use boot option ignore_rlimit_data.
sctp: [Deprecated]: syz-executor2 (pid 8264) Use of struct sctp_assoc_value in delayed_ack socket option.
Use struct sctp_sack_info instead
sctp: [Deprecated]: syz-executor2 (pid 8286) Use of struct sctp_assoc_value in delayed_ack socket option.
Use struct sctp_sack_info instead
audit: type=1326 audit(1503790814.182:1390): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=8327 comm="syz-executor4" exe="/syz-executor4" sig=31 arch=c000003e syscall=202 compat=0 ip=0x446749 code=0xffff0000
audit: type=1326 audit(1503790814.262:1391): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=8327 comm="syz-executor4" exe="/syz-executor4" sig=31 arch=c000003e syscall=202 compat=0 ip=0x446749 code=0xffff0000
TCP: request_sock_TCP: Possible SYN flooding on port 20016. Sending cookies.  Check SNMP counters.
sctp: [Deprecated]: syz-executor0 (pid 8650) Use of int in max_burst socket option deprecated.
Use struct sctp_assoc_value instead
sctp: [Deprecated]: syz-executor0 (pid 8650) Use of int in max_burst socket option deprecated.
Use struct sctp_assoc_value instead
ALSA: seq fatal error: cannot create timer (-19)
ALSA: seq fatal error: cannot create timer (-19)
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
QAT: Invalid ioctl
selinux_nlmsg_perm: 3 callbacks suppressed
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=14606 sclass=netlink_route_socket pig=8842 comm=syz-executor5
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=55705 sclass=netlink_route_socket pig=8842 comm=syz-executor5
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=14606 sclass=netlink_route_socket pig=8842 comm=syz-executor5
audit: type=1326 audit(1503790816.264:1392): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=9019 comm="syz-executor2" exe="/syz-executor2" sig=31 arch=c000003e syscall=202 compat=0 ip=0x446749 code=0xffff0000
QAT: Invalid ioctl
kvm: MONITOR instruction emulated as NOP!
QAT: Invalid ioctl
semctl(GETNCNT/GETZCNT) is since 3.16 Single Unix Specification compliant.
The task syz-executor5 (9108) triggered the difference, watch for misbehavior.
nla_parse: 14 callbacks suppressed
netlink: 11 bytes leftover after parsing attributes in process `syz-executor4'.
netlink: 11 bytes leftover after parsing attributes in process `syz-executor4'.
netlink: 3 bytes leftover after parsing attributes in process `syz-executor2'.
netlink: 3 bytes leftover after parsing attributes in process `syz-executor2'.
netlink: 3 bytes leftover after parsing attributes in process `syz-executor2'.
netlink: 3 bytes leftover after parsing attributes in process `syz-executor2'.
loop_reread_partitions: partition scan of loop0 (›˜ïtÆ?˜õ`³ÄJò£zìP[ëà Œp¤Ï>‰TK6Cî=Ô"à÷Lù­ ¨¹l†œ!¨V#´F-°ü') failed (rc=-13)
audit: type=1326 audit(1503790816.730:1393): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=9295 comm="syz-executor5" exe="/syz-executor5" sig=31 arch=c000003e syscall=202 compat=0 ip=0x446749 code=0xffff0000
device syz3 entered promiscuous mode
device syz3 left promiscuous mode
device syz3 entered promiscuous mode
device syz3 left promiscuous mode
QAT: Invalid ioctl
QAT: Invalid ioctl

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2017/08/26 23:40 linux-next 7159188b70e3 4074aed7 .config console log report ci-upstream-next-kasan-gce
* Struck through repros no longer work on HEAD.