From: Catalin Marinas <catalin.marinas@arm.com>
To: Breno Leitao <leitao@debian.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Waiman Long <llong@redhat.com>, Gu Bowen <gubowen5@huawei.com>,
stable@vger.kernel.org, linux-mm@kvack.org,
Lu Jialin <lujialin4@huawei.com>
Subject: Re: [PATCH] mm: Fix possible deadlock in console_trylock_spinning
Date: Mon, 4 Aug 2025 19:28:42 +0100 [thread overview]
Message-ID: <aJD72syGyJs203Mw@arm.com> (raw)
In-Reply-To: <o2gpvdtxqrdfrsbayorvzvjqcreb45puojpgfye7dimbuuvbdt@gxquukahrxo7>
On Mon, Aug 04, 2025 at 05:34:10AM -0700, Breno Leitao wrote:
> On Mon, Aug 04, 2025 at 01:08:15PM +0100, Catalin Marinas wrote:
>
> > I'm surprised we haven't seen these until recently. Has printk always
> > allocated memory?
>
> I can talk about netconsole, and the answer is yes!
>
> weird enought, lockdep never picked this issue, and I have a few set of
> hosts running kmemleak and lockdep for a while.
>
> This time was different because I have decided to invstiage the code,
> and found the deadlock. Still, no lockdep complain at all.
I guess it's because kmemleak is quiet in general, unless problems are
found, and lockdep never registered this combination - printk() called
with the kmemleak_lock held.
Thanks for investigating.
--
Catalin
next prev parent reply other threads:[~2025-08-04 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 9:49 Gu Bowen
2025-08-01 22:33 ` Andrew Morton
2025-08-02 3:09 ` Waiman Long
2025-08-02 3:53 ` Andrew Morton
2025-08-04 12:08 ` Catalin Marinas
2025-08-04 12:34 ` Breno Leitao
2025-08-04 18:28 ` Catalin Marinas [this message]
2025-08-05 7:44 ` Gu Bowen
2025-08-06 15:34 ` John Ogness
2025-08-07 3:22 ` Gu Bowen
2025-08-01 23:52 ` Andrew Morton
2025-08-11 14:33 ` Petr Mladek
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=aJD72syGyJs203Mw@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=gubowen5@huawei.com \
--cc=leitao@debian.org \
--cc=linux-mm@kvack.org \
--cc=llong@redhat.com \
--cc=lujialin4@huawei.com \
--cc=stable@vger.kernel.org \
/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