[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <swdpckuwwlv3uiessmtnf2jwlx3jusw6u7fpk5iggqo4t2vdws@7rpjso4gr7qp>
Date: Tue, 23 Sep 2025 05:30:03 -0700
From: Breno Leitao <leitao@...ian.org>
To: John Ogness <john.ogness@...utronix.de>
Cc: Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <senozhatsky@...omium.org>, Steven Rostedt <rostedt@...dmis.org>,
Mike Galbraith <efault@....de>, linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH printk v1 1/1] printk: nbcon: Allow unsafe write_atomic()
for panic
Hello John,
On Mon, Sep 22, 2025 at 12:50:04PM +0206, John Ogness wrote:
> On 2025-09-17, Petr Mladek <pmladek@...e.com> wrote:
> @Breno: Or were you planning on pushing the nbcon netconsole for the 6.18
> merge window next week? (I would guess no.)
Unfortuantely no, for me to get netconsole on top of nbcon, I need to
address a few dependencies:
1) Get the memleak fixed, given this is conflicting with the next item
* https://lore.kernel.org/all/20250918-netconsole_torture-v5-0-77e25e0a4eb6@debian.org/
2) Decouple netconsole from netpoll
* https://lore.kernel.org/all/20250902-netpoll_untangle_v3-v1-0-51a03d6411be@debian.org/#t
3) Convert the target_list_lock to RCU, to avoid having to disable IRQ
at netconsole side.
4) Move netconsole to nbcon.
Given that these are "core" changes, I would prefer to get, at least, 3)
and 4) into the next (6.19) merge window.
Thanks for asking,
--breno
Powered by blists - more mailing lists