From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
John Ogness <john.ogness@linutronix.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [next-20240925] possible circular locking: uart vs kmemleak
Date: Thu, 26 Sep 2024 23:41:59 +0900 [thread overview]
Message-ID: <20240926144159.GF11458@google.com> (raw)
In-Reply-To: <ZvViU8vmNiXhCjKX@pathway.suse.cz>
On (24/09/26 15:32), Petr Mladek wrote:
> On Thu 2024-09-26 13:07:15, Sergey Senozhatsky wrote:
> > Greetings,
> >
> > Ran into the following issue today. It's sort of interesting, not sure
> > what even to do about it. The
> >
> > uart -> tty -> mm /* kmalloc -> kmemleak */
> >
> > chain looks problematic, it certainly overlaps with
> >
> > mm -> printk -> uart /* which can kmalloc and re-enter mm -> kmemleak? */
>
> I believe that it will get solved by the uart console driver
> conversion to nbcon. I should remove the path:
>
> printk -> uart
>
> or more precisely, it should remove the path:
>
> console_owner --> &port_lock_key
>
> The patchset with the uart 8250 console driver conversion is still
> pending a review, see the last version at
> https://lore.kernel.org/r/20240913140538.221708-1-john.ogness@linutronix.de
It does fix the issue for me, you are right. Thanks for the pointers.
prev parent reply other threads:[~2024-09-26 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 4:07 [next-20240925] possible circular locking: uart vs kmemleak Sergey Senozhatsky
2024-09-26 13:32 ` Petr Mladek
2024-09-26 14:41 ` Sergey Senozhatsky [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=20240926144159.GF11458@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-serial@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.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 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.