From: David Sterba <dsterba@suse.cz>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Filipe Manana <fdmanana@gmail.com>,
Peter Zijlstra <peterz@infradead.org>, Jan Kara <jack@suse.cz>,
David Sterba <dsterba@suse.com>,
Nikolay Borisov <nborisov@suse.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [RFC] fs: Avoid to use lockdep information if it's turned off
Date: Fri, 13 Nov 2020 18:19:28 +0100 [thread overview]
Message-ID: <20201113171927.GG6756@suse.cz> (raw)
In-Reply-To: <20201112032212.GF3025@boqun-archlinux>
On Thu, Nov 12, 2020 at 11:22:12AM +0800, Boqun Feng wrote:
> For the "BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!" warning, do you see
> that every time when you run xfstests and don't see other lockdep
> splats? If so, that means we reach the limitation of number of lockdep
> hlock chains, and we should fix that.
It's not every time and depends on the release, eg. I found no reports
in a sample log for 5.7..5.9, while there are many for 5.2..5.6 and
5.10, every 2nd or 3rd run.
[ 0.185150] ... MAX_LOCKDEP_SUBCLASSES: 8
[ 0.186202] ... MAX_LOCK_DEPTH: 48
[ 0.187286] ... MAX_LOCKDEP_KEYS: 8192
[ 0.188404] ... CLASSHASH_SIZE: 4096
[ 0.189519] ... MAX_LOCKDEP_ENTRIES: 32768
[ 0.190672] ... MAX_LOCKDEP_CHAINS: 65536
[ 0.191814] ... CHAINHASH_SIZE: 32768
prev parent reply other threads:[~2020-11-13 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 1:37 [RFC] fs: Avoid to use lockdep information if it's turned off Boqun Feng
2020-11-10 1:49 ` Darrick J. Wong
2020-11-10 5:40 ` Boqun Feng
2020-11-10 16:49 ` Darrick J. Wong
2020-11-10 15:33 ` David Sterba
2020-11-11 14:01 ` David Sterba
2020-11-12 3:22 ` Boqun Feng
2020-11-13 17:19 ` David Sterba [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=20201113171927.GG6756@suse.cz \
--to=dsterba@suse.cz \
--cc=boqun.feng@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=dsterba@suse.com \
--cc=fdmanana@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nborisov@suse.com \
--cc=peterz@infradead.org \
--cc=viro@zeniv.linux.org.uk \
/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.