[syzbot] BUG: MAX_LOCKDEP_CHAINS too low! (3)

[syzbot] BUG: MAX_LOCKDEP_CHAINS too low! (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    66f4beaa6c1d Merge branch 'linus' of git://git.kernel.org/..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16adc769b00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a262045c4c15a9e0
dashboard link: https://syzkaller.appspot.com/bug?extid=8a249628ae32ea7de3a2
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+8a249628ae32ea7de3a2@syzkaller.appspotmail.com

BUG: MAX_LOCKDEP_CHAINS too low!
turning off the locking correctness validator.
CPU: 0 PID: 31504 Comm: kworker/u4:13 Not tainted 5.15.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: bond1944 bond_mii_monitor
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 add_chain_cache kernel/locking/lockdep.c:3649 [inline]
 lookup_chain_cache_add kernel/locking/lockdep.c:3748 [inline]
 validate_chain kernel/locking/lockdep.c:3769 [inline]
 __lock_acquire.cold+0x372/0x3ab kernel/locking/lockdep.c:5027
 lock_acquire kernel/locking/lockdep.c:5637 [inline]
 lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5602
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
 _raw_spin_lock_irqsave+0x39/0x50 kernel/locking/spinlock.c:162
 lock_timer_base+0x5a/0x1f0 kernel/time/timer.c:946
 __mod_timer+0x398/0xe30 kernel/time/timer.c:1019
 __queue_delayed_work+0x1a7/0x270 kernel/workqueue.c:1678
 queue_delayed_work_on+0x105/0x120 kernel/workqueue.c:1703
 queue_delayed_work include/linux/workqueue.h:517 [inline]
 bond_mii_monitor+0x95b/0x1af0 drivers/net/bonding/bond_main.c:2759
 process_one_work+0x9b2/0x1690 kernel/workqueue.c:2298
 worker_thread+0x658/0x11f0 kernel/workqueue.c:2445
 kthread+0x405/0x4f0 kernel/kthread.c:327
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </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.

Re: [syzbot] BUG: MAX_LOCKDEP_CHAINS too low! (3)

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit:    6f513529296f Merge tag 'for-5.16-rc4-tag' of git://git.ker..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10a8954db00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=221ffc09e39ebbd1
dashboard link: https://syzkaller.appspot.com/bug?extid=8a249628ae32ea7de3a2
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12777551b00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15a99a05b00000

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

BUG: MAX_LOCKDEP_CHAINS too low!
turning off the locking correctness validator.
CPU: 0 PID: 6709 Comm: kworker/u4:7 Not tainted 5.16.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: bond1948 bond_netdev_notify_work
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 add_chain_cache kernel/locking/lockdep.c:3649 [inline]
 lookup_chain_cache_add kernel/locking/lockdep.c:3748 [inline]
 validate_chain kernel/locking/lockdep.c:3769 [inline]
 __lock_acquire.cold+0x372/0x3ab kernel/locking/lockdep.c:5027
 lock_acquire kernel/locking/lockdep.c:5637 [inline]
 lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5602
 process_one_work+0x921/0x1690 kernel/workqueue.c:2274
 worker_thread+0x658/0x11f0 kernel/workqueue.c:2445
 kthread+0x405/0x4f0 kernel/kthread.c:327
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>

Re: [syzbot] Re: BUG: MAX_LOCKDEP_CHAINS too low! (3)

[syzbot]

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: Re: BUG: MAX_LOCKDEP_CHAINS too low! (3)
Author: david@fromorbit.com

On Wed, Mar 06, 2024 at 11:58:18AM +1100, Dave Chinner wrote:
> 
> Lockdep is hitting the maximum dependency chain tracker size:
> 
> VM DIAGNOSIS:
>  lock-classes:                         4657 [max: 8192]
>  direct dependencies:                 23720 [max: 131072]
>  indirect dependencies:              274342
>  all direct dependencies:           1053416
>  dependency chains:                   65377 [max: 65536]
> 
> Some of the reproducers don't involve XFS at all, but all seem to
> show something like:
> 
>  dependency chains:                  131072 [max: 131072]
> 
> So this is a core kernel or syzkaller kernel config issue and not
> an XFS issue.
> 
> # syz subsystems: kernel

Ugh. try this again:

#syz set subsystems: kernel


-- 
Dave Chinner
david@fromorbit.com