lkml.org 
[lkml]   [2022]   [Jul]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
Subject[syzbot] WARNING in match_held_lock
From
Hello,

syzbot found the following issue on:

HEAD commit: 849f35422319 Merge tag 'thunderbolt-for-v5.20-rc1' of git:..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=12f9d498080000
kernel config: https://syzkaller.appspot.com/x/.config?x=33f1eaa5b20a699
dashboard link: https://syzkaller.appspot.com/bug?extid=6c67d4224af196c99976
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

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

------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(!hlock->nest_lock)
WARNING: CPU: 0 PID: 4591 at kernel/locking/lockdep.c:5135 match_held_lock+0xad/0xc0 kernel/locking/lockdep.c:5135
Modules linked in:
CPU: 0 PID: 4591 Comm: syz-executor.0 Not tainted 5.19.0-rc4-syzkaller-00090-g849f35422319 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:match_held_lock+0xad/0xc0 kernel/locking/lockdep.c:5135
Code: e8 f8 2d 24 fc 85 c0 74 e4 8b 05 a6 16 ef 02 85 c0 75 da 48 c7 c6 a0 95 47 86 48 c7 c7 20 92 47 86 89 44 24 04 e8 03 9a d1 ff <0f> 0b 8b 44 24 04 eb bd 66 66 2e 0f 1f 84 00 00 00 00 00 41 57 41
RSP: 0018:ffffc9000c997d50 EFLAGS: 00010086
RAX: 0000000000000000 RBX: ffff88811600cb68 RCX: 0000000000000000
RDX: ffff88811600b900 RSI: ffffffff812c0fe8 RDI: fffff52001932f9c
RBP: ffffffff87a94640 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000003 R11: 776172206373696d R12: ffff88811600b900
R13: ffff88811600c2f8 R14: 00000000ffffffff R15: ffff88811600cb68
FS: 00007f684e67c700(0000) GS:ffff8881f6800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f684e639fc0 CR3: 00000001376c9000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__lock_is_held kernel/locking/lockdep.c:5406 [inline]
lock_is_held_type+0xa7/0x140 kernel/locking/lockdep.c:5708
lock_is_held include/linux/lockdep.h:279 [inline]
rcu_read_lock_sched_held+0x3a/0x70 kernel/rcu/update.c:125
trace_lock_acquire include/trace/events/lock.h:24 [inline]
lock_acquire+0x480/0x570 kernel/locking/lockdep.c:5636
do_write_seqcount_begin_nested include/linux/seqlock.h:516 [inline]
do_write_seqcount_begin include/linux/seqlock.h:541 [inline]
vtime_task_switch_generic+0xb5/0x5a0 kernel/sched/cputime.c:768
vtime_task_switch include/linux/vtime.h:95 [inline]
finish_task_switch.isra.0+0x4e3/0xa10 kernel/sched/core.c:5020
schedule_tail+0x7/0xd0 kernel/sched/core.c:5082
ret_from_fork+0x8/0x30 arch/x86/entry/entry_64.S:287
</TASK>


---
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 syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

\
 
 \ /
  Last update: 2022-07-03 21:59    [W:0.037 / U:3.272 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site