[moderation] [kernel?] KCSAN: data-race in data_push_tail / symbol_string (6)

0 views
Skip to first unread message

syzbot

unread,
Dec 5, 2023, 8:41:34 AM12/5/23
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: f1a09972a45a Merge tag 'ata-6.7-rc3' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10805b44e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c1151391aefc0c3
dashboard link: https://syzkaller.appspot.com/bug?extid=79b1bc982d9175035a4e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [b...@alien8.de dave....@linux.intel.com h...@zytor.com jpoi...@kernel.org linux-...@vger.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.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/dffb0d99ad2d/disk-f1a09972.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/080ad4a9580e/vmlinux-f1a09972.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f1ac25646188/bzImage-f1a09972.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+79b1bc...@syzkaller.appspotmail.com

8021q: adding VLAN 0 to HW filter on device batadv3911
bond2034: (slave batadv3911): Enslaving as a backup interface with an up link
==================================================================
BUG: KCSAN: data-race in data_push_tail / symbol_string

write to 0xffffffff86eaeae9 of 1 bytes by task 12674 on cpu 1:
string_nocheck lib/vsprintf.c:650 [inline]
symbol_string+0x1b6/0x240 lib/vsprintf.c:1006
pointer+0x77a/0xd10 lib/vsprintf.c:2417
vsnprintf+0x861/0xe20 lib/vsprintf.c:2823
vscnprintf+0x42/0x80 lib/vsprintf.c:2925
printk_sprint+0x30/0x2d0 kernel/printk/printk.c:2124
vprintk_store+0x56f/0x800 kernel/printk/printk.c:2238
vprintk_emit+0xd0/0x5d0 kernel/printk/printk.c:2284
vprintk_default+0x26/0x30 kernel/printk/printk.c:2318
vprintk+0x71/0x80 kernel/printk/printk_safe.c:45
_printk+0x7a/0xa0 kernel/printk/printk.c:2328
printk_stack_address arch/x86/kernel/dumpstack.c:72 [inline]
show_trace_log_lvl+0x42e/0x510 arch/x86/kernel/dumpstack.c:285
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xda/0x130 lib/dump_stack.c:106
dump_stack+0x15/0x20 lib/dump_stack.c:113
fail_dump lib/fault-inject.c:52 [inline]
should_fail_ex+0x21f/0x230 lib/fault-inject.c:153
__should_failslab+0x92/0xa0 mm/failslab.c:44
should_failslab+0x9/0x20 mm/slab_common.c:1493
slab_pre_alloc_hook mm/slab.h:712 [inline]
slab_alloc_node mm/slub.c:3460 [inline]
slab_alloc mm/slub.c:3486 [inline]
__kmem_cache_alloc_lru mm/slub.c:3493 [inline]
kmem_cache_alloc+0x4e/0x250 mm/slub.c:3502
skb_clone+0x154/0x1e0 net/core/skbuff.c:1916
netlink_skb_clone include/linux/netlink.h:252 [inline]
nfnetlink_rcv_batch net/netfilter/nfnetlink.c:388 [inline]
nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:639 [inline]
nfnetlink_rcv+0x2ea/0x13b0 net/netfilter/nfnetlink.c:657
netlink_unicast_kernel net/netlink/af_netlink.c:1342 [inline]
netlink_unicast+0x589/0x650 net/netlink/af_netlink.c:1368
netlink_sendmsg+0x66e/0x770 net/netlink/af_netlink.c:1910
sock_sendmsg_nosec net/socket.c:730 [inline]
__sock_sendmsg net/socket.c:745 [inline]
____sys_sendmsg+0x37c/0x4d0 net/socket.c:2584
___sys_sendmsg net/socket.c:2638 [inline]
__sys_sendmsg+0x1e9/0x270 net/socket.c:2667
__do_sys_sendmsg net/socket.c:2676 [inline]
__se_sys_sendmsg net/socket.c:2674 [inline]
__x64_sys_sendmsg+0x46/0x50 net/socket.c:2674
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffffffff86eaeae8 of 8 bytes by task 12679 on cpu 0:
data_make_reusable kernel/printk/printk_ringbuffer.c:590 [inline]
data_push_tail+0x102/0x430 kernel/printk/printk_ringbuffer.c:675
data_alloc+0xbe/0x2c0 kernel/printk/printk_ringbuffer.c:1046
prb_reserve+0x893/0xbc0 kernel/printk/printk_ringbuffer.c:1555
vprintk_store+0x53e/0x800 kernel/printk/printk.c:2228
vprintk_emit+0xd0/0x5d0 kernel/printk/printk.c:2284
vprintk_default+0x26/0x30 kernel/printk/printk.c:2318
vprintk+0x71/0x80 kernel/printk/printk_safe.c:45
_printk+0x7a/0xa0 kernel/printk/printk.c:2328
__netdev_printk+0x2bf/0x3b0 net/core/dev.c:11444
netdev_info+0x99/0xc0 net/core/dev.c:11491
bond_enslave+0x1fa7/0x2040 drivers/net/bonding/bond_main.c:2274
do_set_master net/core/rtnetlink.c:2710 [inline]
rtnl_newlink_create net/core/rtnetlink.c:3538 [inline]
__rtnl_newlink net/core/rtnetlink.c:3741 [inline]
rtnl_newlink+0x1497/0x1670 net/core/rtnetlink.c:3754
rtnetlink_rcv_msg+0x807/0x8c0 net/core/rtnetlink.c:6558
netlink_rcv_skb+0x126/0x220 net/netlink/af_netlink.c:2545
rtnetlink_rcv+0x1c/0x20 net/core/rtnetlink.c:6576
netlink_unicast_kernel net/netlink/af_netlink.c:1342 [inline]
netlink_unicast+0x589/0x650 net/netlink/af_netlink.c:1368
netlink_sendmsg+0x66e/0x770 net/netlink/af_netlink.c:1910
sock_sendmsg_nosec net/socket.c:730 [inline]
__sock_sendmsg net/socket.c:745 [inline]
____sys_sendmsg+0x37c/0x4d0 net/socket.c:2584
___sys_sendmsg net/socket.c:2638 [inline]
__sys_sendmsg+0x1e9/0x270 net/socket.c:2667
__do_sys_sendmsg net/socket.c:2676 [inline]
__se_sys_sendmsg net/socket.c:2674 [inline]
__x64_sys_sendmsg+0x46/0x50 net/socket.c:2674
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x0000000100003eae -> 0x6f6c635f626b7320

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 12679 Comm: syz-executor.4 Not tainted 6.7.0-rc2-syzkaller-00147-gf1a09972a45a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
==================================================================
syz-executor.4 (12679) used greatest stack depth: 8920 bytes left


---
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Dec 29, 2023, 11:49:12 AM12/29/23
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