mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chris Murphy" <lists@colorremedies.com>
To: "Mirsad Goran Todorovac" <mirsad.todorovac@alu.unizg.hr>,
	"David Sterba" <dsterba@suse.cz>
Cc: "Btrfs BTRFS" <linux-btrfs@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Chris Mason" <clm@fb.com>, "Josef Bacik" <josef@toxicpanda.com>,
	"David Sterba" <dsterba@suse.com>
Subject: Re: [BUG] btrfs: MAX_LOCKDEP_CHAIN_HLOCKS too low!
Date: Tue, 27 Jun 2023 14:49:15 -0400	[thread overview]
Message-ID: <0943bc38-34a4-4c38-8e91-9aa6446fb15a@app.fastmail.com> (raw)
In-Reply-To: <ca3f483e-38fc-786b-d85b-35d543a701a9@alu.unizg.hr>



On Tue, Jun 27, 2023, at 12:27 PM, Mirsad Goran Todorovac wrote:

> Thank you for your prompt response. It wasn't obvious from the kernel
> message though which .config setting needs adjustment.


https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2271


> I am yet unable to tell whether the lockdep setting being too low and
> turning off the locking correctness validator caused the kernel crash, but
> I will know more after restarting the kselftest with the new lockdep
> setting ...

Lockdep is complex and so are real file system workloads, so the warnings might seem transient.

-- 
Chris Murphy

      parent reply	other threads:[~2023-06-27 18:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 23:40 Mirsad Goran Todorovac
2023-06-27  0:19 ` Qu Wenruo
     [not found]   ` <20230627142739.GB16168@twin.jikos.cz>
2023-06-27 16:27     ` Mirsad Goran Todorovac
2023-06-27 18:16       ` Mirsad Goran Todorovac
2023-06-27 18:49       ` Chris Murphy [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=0943bc38-34a4-4c38-8e91-9aa6446fb15a@app.fastmail.com \
    --to=lists@colorremedies.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mirsad.todorovac@alu.unizg.hr \
    /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

all inboxes | Powered by JetHome®