KCSAN: data-race in do_signal_stop / prepare_signal

9 views
Skip to first unread message

syzbot

unread,
Jan 24, 2020, 6:57:10 AM1/24/20
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 245a4300 Merge branch 'rcu/kcsan' into tip/locking/kcsan
git tree: https://github.com/google/ktsan.git kcsan
console output: https://syzkaller.appspot.com/x/log.txt?x=17883d76e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a4b9db179318d21f
dashboard link: https://syzkaller.appspot.com/bug?extid=60abfb3e5fb112d5a211
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
CC: [chri...@brauner.io ebie...@xmission.com linux-...@vger.kernel.org ol...@redhat.com el...@google.com]

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

==================================================================
BUG: KCSAN: data-race in do_signal_stop / prepare_signal

read to 0xffff8881001f10a4 of 4 bytes by interrupt on cpu 0:
sig_task_ignored kernel/signal.c:94 [inline]
sig_ignored kernel/signal.c:119 [inline]
prepare_signal+0x1f5/0x7a0 kernel/signal.c:956
send_sigqueue+0xc1/0x4b0 kernel/signal.c:1859
posix_timer_event kernel/time/posix-timers.c:328 [inline]
posix_timer_fn+0x10d/0x230 kernel/time/posix-timers.c:354
__run_hrtimer kernel/time/hrtimer.c:1517 [inline]
__hrtimer_run_queues+0x274/0x5f0 kernel/time/hrtimer.c:1579
hrtimer_interrupt+0x22a/0x480 kernel/time/hrtimer.c:1641
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1110 [inline]
smp_apic_timer_interrupt+0xdc/0x280 arch/x86/kernel/apic/apic.c:1135
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:829
__read_once_size include/linux/compiler.h:232 [inline]
arch_atomic64_read arch/x86/include/asm/atomic64_64.h:22 [inline]
atomic64_read include/asm-generic/atomic-instrumented.h:851 [inline]
atomic_long_read include/asm-generic/atomic-long.h:29 [inline]
find_watchpoint kernel/kcsan/core.c:96 [inline]
check_access kernel/kcsan/core.c:446 [inline]
__tsan_read8+0x34/0x100 kernel/kcsan/core.c:589
compound_head include/linux/page-flags.h:174 [inline]
PageSwapBacked include/linux/page-flags.h:340 [inline]
mm_counter_file include/linux/mm.h:1657 [inline]
alloc_set_pte+0x385/0xf50 mm/memory.c:3402
finish_fault+0xdb/0x180 mm/memory.c:3448
do_shared_fault mm/memory.c:3658 [inline]
do_fault mm/memory.c:3718 [inline]
handle_pte_fault mm/memory.c:3945 [inline]
__handle_mm_fault+0x1e83/0x2e00 mm/memory.c:4075
handle_mm_fault+0x21b/0x530 mm/memory.c:4112
do_user_addr_fault arch/x86/mm/fault.c:1441 [inline]
__do_page_fault+0x456/0x8d0 arch/x86/mm/fault.c:1506
do_page_fault+0x38/0x194 arch/x86/mm/fault.c:1530
page_fault+0x34/0x40 arch/x86/entry/entry_64.S:1203

write to 0xffff8881001f10a4 of 4 bytes by task 9576 on cpu 1:
freezer_count include/linux/freezer.h:121 [inline]
freezable_schedule include/linux/freezer.h:173 [inline]
do_signal_stop+0x204/0x500 kernel/signal.c:2390
get_signal+0x61b/0x1320 kernel/signal.c:2694
do_signal+0x2f/0x6c0 arch/x86/kernel/signal.c:815
exit_to_usermode_loop+0x250/0x2c0 arch/x86/entry/common.c:160
prepare_exit_to_usermode arch/x86/entry/common.c:195 [inline]
syscall_return_slowpath arch/x86/entry/common.c:278 [inline]
do_syscall_64+0x384/0x3a0 arch/x86/entry/common.c:304
entry_SYSCALL_64_after_hwframe+0x44/0xa9

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


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

unread,
Jun 24, 2021, 9:29:12 PM6/24/21
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