From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, Sashiko <sashiko-bot@kernel.org>
Subject: Re: [PATCH printk] printk: Fix possible console use-after-free
Date: Tue, 07 Jul 2026 15:26:51 +0206 [thread overview]
Message-ID: <87qzlf0wcs.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <akz5fElnOdUFe2fA@pathway.suse.cz>
On 2026-07-07, Petr Mladek <pmladek@suse.com> wrote:
> Now, the question is whether I should rush it into 7.2-rcX or
> it might wait for 7.3.
>
> IMHO, it can wait for 7.3 because it is very hard to trigger.
> All console drivers have "struct console" defined in the static .data
> section. It can disappear only when it is added as a module and
> the module gets removed. Which is a rather complicated and long
> process.
I am fine with it waiting until 7.3.
John
next prev parent reply other threads:[~2026-07-07 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 14:14 [PATCH printk] printk: Fix possible console use-after-free John Ogness
2026-07-07 13:05 ` Petr Mladek
2026-07-07 13:20 ` John Ogness [this message]
2026-07-09 13:59 ` 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=87qzlf0wcs.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sashiko-bot@kernel.org \
--cc=senozhatsky@chromium.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