From: Christoph Hellwig <hch@lst.de>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: Ming Lei <ming.lei@redhat.com>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>,
linux-block@vger.kernel.org
Subject: Re: Blockdev 6.13-rc lockdep splat regressions
Date: Fri, 10 Jan 2025 11:14:51 +0100 [thread overview]
Message-ID: <20250110101451.GA12633@lst.de> (raw)
In-Reply-To: <65a8ef7321bf905ab27c383395016fe299f6dfd9.camel@linux.intel.com>
On Fri, Jan 10, 2025 at 11:12:58AM +0100, Thomas Hellström wrote:
> Ming, Others
>
> On 6.13-rc6 I'm seeing a couple of lockdep splats which appear
> introduced by the commit
>
> f1be1788a32e ("block: model freeze & enter queue as lock for supporting
> lockdep")
>
> The first one happens when swap-outs start to a scsi disc,
> Simple reproducer is to start a couple of parallel "gitk" on the kernel
> repo and watch them exhaust available memory.
>
> the second is easily triggered by entering a debugfs trace directory,
> apparently triggering automount:
> cd /sys/kernel/debug/tracing/events
>
> Are you aware of these?
Yes, this series fixes it:
https://lore.kernel.org/linux-block/20250110054726.1499538-1-hch@lst.de/
should be ready now that the nitpicking has settled down.
next prev parent reply other threads:[~2025-01-10 10:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 10:12 Blockdev 6.13-rc lockdep splat regressions Thomas Hellström
2025-01-10 10:14 ` Christoph Hellwig [this message]
2025-01-10 10:21 ` Thomas Hellström
2025-01-10 12:13 ` Ming Lei
2025-01-10 14:36 ` Thomas Hellström
2025-01-11 3:05 ` Ming Lei
2025-01-12 11:33 ` Thomas Hellström
2025-01-12 15:50 ` Ming Lei
2025-01-12 17:44 ` Thomas Hellström
2025-01-13 0:55 ` Ming Lei
2025-01-13 8:48 ` Thomas Hellström
2025-01-13 9:28 ` Ming Lei
2025-01-13 9:58 ` Thomas Hellström
2025-01-13 10:40 ` Ming Lei
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=20250110101451.GA12633@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=thomas.hellstrom@linux.intel.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 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.