KCSAN: data-race in __packet_rcv_has_room / copy_page_from_iter

6 views
Skip to first unread message

syzbot

unread,
Dec 11, 2021, 4:05:24 AM12/11/21
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 0fcfb00b28c0 Linux 5.16-rc4
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14411badb00000
kernel config: https://syzkaller.appspot.com/x/.config?x=9a2598dd2cfceb9b
dashboard link: https://syzkaller.appspot.com/bug?extid=b5b6fdf0602b33029c5d
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [and...@kernel.org a...@kernel.org b...@vger.kernel.org dan...@iogearbox.net da...@davemloft.net edum...@google.com john.fa...@gmail.com ka...@fb.com kps...@kernel.org ku...@kernel.org linux-...@vger.kernel.org net...@vger.kernel.org pa...@netfilter.org songliu...@fb.com yajun...@linux.dev y...@fb.com]

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

==================================================================
BUG: KCSAN: data-race in __packet_rcv_has_room / copy_page_from_iter

read to 0xffff888137fb0000 of 8 bytes by interrupt on cpu 0:
__packet_get_status net/packet/af_packet.c:437 [inline]
packet_lookup_frame net/packet/af_packet.c:525 [inline]
__tpacket_has_room net/packet/af_packet.c:1256 [inline]
__packet_rcv_has_room+0x279/0x450 net/packet/af_packet.c:1297
tpacket_rcv+0x2da/0x24e0 net/packet/af_packet.c:2272
deliver_skb net/core/dev.c:2218 [inline]
__netif_receive_skb_core+0x415/0x1df0 net/core/dev.c:5309
__netif_receive_skb_one_core net/core/dev.c:5463 [inline]
__netif_receive_skb+0x52/0x1b0 net/core/dev.c:5579
process_backlog+0x23f/0x3e0 net/core/dev.c:6455
__napi_poll+0x65/0x3f0 net/core/dev.c:7023
napi_poll net/core/dev.c:7090 [inline]
net_rx_action+0x29e/0x650 net/core/dev.c:7177
__do_softirq+0x158/0x2de kernel/softirq.c:558
do_softirq+0xb1/0xf0 kernel/softirq.c:459
__local_bh_enable_ip+0x68/0x70 kernel/softirq.c:383
local_bh_enable+0x1b/0x20 include/linux/bottom_half.h:33
rcu_read_unlock_bh include/linux/rcupdate.h:758 [inline]
__dev_queue_xmit+0x597/0xf70 net/core/dev.c:4256
dev_queue_xmit+0x13/0x20 net/core/dev.c:4262
batadv_send_skb_packet+0x23f/0x2a0 net/batman-adv/send.c:108
batadv_send_broadcast_skb+0x20/0x30 net/batman-adv/send.c:127
batadv_iv_ogm_send_to_if net/batman-adv/bat_iv_ogm.c:393 [inline]
batadv_iv_ogm_emit net/batman-adv/bat_iv_ogm.c:421 [inline]
batadv_iv_send_outstanding_bat_ogm_packet+0x40e/0x4c0 net/batman-adv/bat_iv_ogm.c:1701
process_one_work+0x3fc/0x980 kernel/workqueue.c:2298
worker_thread+0x616/0xa70 kernel/workqueue.c:2445
kthread+0x2c7/0x2e0 kernel/kthread.c:327
ret_from_fork+0x1f/0x30

write to 0xffff888137fb0000 of 4096 bytes by task 11881 on cpu 1:
instrument_copy_from_user include/linux/instrumented.h:136 [inline]
copyin lib/iov_iter.c:167 [inline]
copy_page_from_iter_iovec lib/iov_iter.c:312 [inline]
copy_page_from_iter+0x24e/0x510 lib/iov_iter.c:902
process_vm_rw_pages mm/process_vm_access.c:43 [inline]
process_vm_rw_single_vec+0x274/0x460 mm/process_vm_access.c:117
process_vm_rw_core mm/process_vm_access.c:215 [inline]
process_vm_rw+0x3dd/0x570 mm/process_vm_access.c:283
__do_sys_process_vm_writev mm/process_vm_access.c:303 [inline]
__se_sys_process_vm_writev mm/process_vm_access.c:298 [inline]
__x64_sys_process_vm_writev+0x76/0x90 mm/process_vm_access.c:298
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 11881 Comm: syz-executor.2 Not tainted 5.16.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================


---
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,
Jan 10, 2022, 11:02:19 AM1/10/22
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