From: syzbot <syzbot+de8e83db70e8beedd556@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] INFO: rcu detected stall in sys_socket (10)
Date: Mon, 04 Dec 2023 18:47:04 -0800 [thread overview]
Message-ID: <000000000000eb7a4a060bba3f37@google.com> (raw)
In-Reply-To: <tencent_BBCFCCBEA7F006EC92C9C67209B76EFDAE06@qq.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
INFO: rcu detected stall in validate_mm
rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 1-...D } 2651 jiffies s: 2425 root: 0x2/.
rcu: blocking rcu_node structures (internal RCU debug):
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 5512 Comm: sed Not tainted 6.7.0-rc3-syzkaller-00024-g18d46e76d7c2-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
RIP: 0010:__lock_acquire+0xc89/0x3b20 kernel/locking/lockdep.c:5134
Code: e7 e8 eb 52 ff ff 48 ba 00 00 00 00 00 fc ff df 48 8d 78 40 48 89 f9 48 c1 e9 03 80 3c 11 00 0f 85 98 2b 00 00 48 83 78 40 00 <0f> 84 7c 13 00 00 0f b7 44 24 08 8b 5c 24 48 8b 4c 24 20 c1 e0 0d
RSP: 0018:ffffc900001f0b40 EFLAGS: 00000082
RAX: ffffffff91f8d970 RBX: 0000000000000000 RCX: 1ffffffff23f1b36
RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffffffff91f8d9b0
RBP: ffffffff91f1bca0 R08: 0000000000000000 R09: fffffbfff23e33f3
R10: ffffffff91f19f9f R11: 0000000000000002 R12: ffff888025676450
R13: ffff888025676449 R14: 00000000000008e1 R15: 0000000000000002
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f588bec5ba8 CR3: 0000000029d0e000 CR4: 0000000000350ef0
Call Trace:
<NMI>
</NMI>
<IRQ>
lock_acquire kernel/locking/lockdep.c:5754 [inline]
lock_acquire+0x1ae/0x520 kernel/locking/lockdep.c:5719
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:351 [inline]
advance_sched+0xd5/0xc60 net/sched/sch_taprio.c:934
__run_hrtimer kernel/time/hrtimer.c:1688 [inline]
__hrtimer_run_queues+0x203/0xc20 kernel/time/hrtimer.c:1752
hrtimer_interrupt+0x31b/0x800 kernel/time/hrtimer.c:1814
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1065 [inline]
__sysvec_apic_timer_interrupt+0x105/0x400 arch/x86/kernel/apic/apic.c:1082
sysvec_apic_timer_interrupt+0x90/0xb0 arch/x86/kernel/apic/apic.c:1076
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:645
RIP: 0010:get_current arch/x86/include/asm/current.h:41 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x4/0x60 kernel/kcov.c:206
Code: 66 0f 1f 44 00 00 f3 0f 1e fa 48 8b be b0 01 00 00 e8 b0 ff ff ff 31 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa <65> 48 8b 14 25 c0 bc 03 00 65 8b 05 74 32 7c 7e a9 00 01 ff 00 48
RSP: 0018:ffffc90004cf7970 EFLAGS: 00000246
RAX: ffff88806a0f4c40 RBX: ffff888028217c00 RCX: ffffffff8a700d11
RDX: ffff888025675940 RSI: ffffffff8a700b05 RDI: 0000000000000000
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000005
R10: 000000000000000f R11: 0000000000000001 R12: 00007f588be4efff
R13: 0000000000000005 R14: 000055dc48e02000 R15: dffffc0000000000
ma_slots lib/maple_tree.c:785 [inline]
mas_get_slot lib/maple_tree.c:6673 [inline]
mas_validate_gaps lib/maple_tree.c:6942 [inline]
mt_validate+0x2771/0x3e90 lib/maple_tree.c:7217
validate_mm+0x9a/0x4b0 mm/mmap.c:288
mmap_region+0x15c8/0x2830 mm/mmap.c:2974
do_mmap+0x893/0xef0 mm/mmap.c:1379
vm_mmap_pgoff+0x1a8/0x3c0 mm/util.c:556
ksys_mmap_pgoff+0x422/0x5b0 mm/mmap.c:1425
__do_sys_mmap arch/x86/kernel/sys_x86_64.c:93 [inline]
__se_sys_mmap arch/x86/kernel/sys_x86_64.c:86 [inline]
__x64_sys_mmap+0x125/0x190 arch/x86/kernel/sys_x86_64.c:86
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x40/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7f588c16cb74
Code: 63 08 44 89 e8 5b 41 5c 41 5d c3 41 89 ca 41 f7 c1 ff 0f 00 00 74 0c c7 05 f5 46 01 00 16 00 00 00 eb 17 b8 09 00 00 00 0f 05 <48> 3d 00 f0 ff ff 76 0c f7 d8 89 05 dc 46 01 00 48 83 c8 ff c3 0f
RSP: 002b:00007ffeec15f508 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00007ffeec15f580 RCX: 00007f588c16cb74
RDX: 0000000000000001 RSI: 0000000000025000 RDI: 00007f588be7d000
RBP: 00007ffeec15f8a0 R08: 0000000000000003 R09: 000000000002e000
R10: 0000000000000812 R11: 0000000000000246 R12: 00007f588c150570
R13: 00007ffeec15f928 R14: 000000000002d9c6 R15: 0000000000000000
</TASK>
Tested on:
commit: 18d46e76 Merge tag 'for-6.7-rc3-tag' of git://git.kern..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=12c9bf2ce80000
kernel config: https://syzkaller.appspot.com/x/.config?x=bb39fe85d254f638
dashboard link: https://syzkaller.appspot.com/bug?extid=de8e83db70e8beedd556
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1340351ce80000
next parent reply other threads:[~2023-12-05 2:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_BBCFCCBEA7F006EC92C9C67209B76EFDAE06@qq.com>
2023-12-05 2:47 ` syzbot [this message]
2023-11-30 15:24 [syzbot] [net?] INFO: rcu detected stall in sys_socket (10) syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000eb7a4a060bba3f37@google.com \
--to=syzbot+de8e83db70e8beedd556@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.