[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <0943bc38-34a4-4c38-8e91-9aa6446fb15a@app.fastmail.com>
Date: Tue, 27 Jun 2023 14:49:15 -0400
From: "Chris Murphy" <lists@...orremedies.com>
To: "Mirsad Goran Todorovac" <mirsad.todorovac@....unizg.hr>,
"David Sterba" <dsterba@...e.cz>
Cc: "Btrfs BTRFS" <linux-btrfs@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
"Chris Mason" <clm@...com>, "Josef Bacik" <josef@...icpanda.com>,
"David Sterba" <dsterba@...e.com>
Subject: Re: [BUG] btrfs: MAX_LOCKDEP_CHAIN_HLOCKS too low!
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
Powered by blists - more mailing lists