public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8a249628ae32ea7de3a2@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Re: BUG: MAX_LOCKDEP_CHAINS too low! (3)
Date: Tue, 05 Mar 2024 17:01:26 -0800	[thread overview]
Message-ID: <00000000000092a1f90612f37f35@google.com> (raw)
In-Reply-To: <00000000000069e12f05d0b78c2d@google.com>

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

      parent reply	other threads:[~2024-03-06  1:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-14  3:47 [syzbot] BUG: MAX_LOCKDEP_CHAINS too low! (3) syzbot
2021-12-11 22:04 ` syzbot
2024-03-06  1:01 ` syzbot [this message]

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=00000000000092a1f90612f37f35@google.com \
    --to=syzbot+8a249628ae32ea7de3a2@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox