linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Waiman Long <llong@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Gu Bowen <gubowen5@huawei.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	stable@vger.kernel.org, linux-mm@kvack.org,
	Lu Jialin <lujialin4@huawei.com>,
	Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH] mm: Fix possible deadlock in console_trylock_spinning
Date: Fri, 1 Aug 2025 23:09:31 -0400	[thread overview]
Message-ID: <5ca375cd-4a20-4807-b897-68b289626550@redhat.com> (raw)
In-Reply-To: <20250801153303.cee42dcfc94c63fb5026bba0@linux-foundation.org>

On 8/1/25 6:33 PM, Andrew Morton wrote:
> On Wed, 30 Jul 2025 17:49:14 +0800 Gu Bowen <gubowen5@huawei.com> wrote:
>
>> kmemleak_scan_thread() invokes scan_block() which may invoke a nomal
>> printk() to print warning message. This can cause a deadlock in the
>> scenario reported below:
>>
>>         CPU0                    CPU1
>>         ----                    ----
>>    lock(kmemleak_lock);
>>                                 lock(&port->lock);
>>                                 lock(kmemleak_lock);
>>    lock(console_owner);
>>
>> To solve this problem, switch to printk_safe mode before printing warning
>> message, this will redirect all printk()-s to a special per-CPU buffer,
>> which will be flushed later from a safe context (irq work), and this
>> deadlock problem can be avoided.
>>
>> Our syztester report the following lockdep error:
>>
>> ...
>>
>> index 4801751cb6b6..d322897a1de1 100644
>> --- a/mm/kmemleak.c
>> +++ b/mm/kmemleak.c
>> @@ -390,9 +390,11 @@ static struct kmemleak_object *lookup_object(unsigned long ptr, int alias)
>>   		else if (object->pointer == ptr || alias)
>>   			return object;
>>   		else {
>> +			__printk_safe_enter();
>>   			kmemleak_warn("Found object by alias at 0x%08lx\n",
>>   				      ptr);
>>   			dump_object_info(object);
>> +			__printk_safe_exit();
>>   			break;
>>   		}
>>   	}
> Thanks.
>
> There have been a few kmemleak locking fixes lately.
>
> I believe this fix is independent from the previous ones:
>
> https://lkml.kernel.org/r/20250731-kmemleak_lock-v1-1-728fd470198f@debian.org
> https://lkml.kernel.org/r/20250728190248.605750-1-longman@redhat.com
>
> But can people please check?

I believe that __printk_safe_enter()/_printk_safe_exit() are for printk 
internal use only. The proper API to use should be 
printk_deferred_enter()/printk_deferred_exit() if we want to deferred 
the printing. Since kmemleak_lock will have been acquired with irq 
disabled, it meets the condition that printk_deferred_*() APIs can be used.

Cheers,
Longman



  reply	other threads:[~2025-08-02  3:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30  9:49 [PATCH] mm: Fix possible deadlock in console_trylock_spinning Gu Bowen
2025-08-01 22:33 ` Andrew Morton
2025-08-02  3:09   ` Waiman Long [this message]
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
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=5ca375cd-4a20-4807-b897-68b289626550@redhat.com \
    --to=llong@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=gubowen5@huawei.com \
    --cc=leitao@debian.org \
    --cc=linux-mm@kvack.org \
    --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;
as well as URLs for NNTP newsgroup(s).