linux-kernel - Re: [PATCH printk v2 1/1] printk: nbcon: Allow unsafe write

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ofk6hbiz4wjux6k4zdlsfglvxeszlxl4at232wcbvlovwjix4i@7e6wfdsf66pj>
Date: Tue, 4 Nov 2025 01:56:07 -0800
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 v2 1/1] printk: nbcon: Allow unsafe write_atomic()
 for panic

Hello John,

On Fri, Oct 31, 2025 at 10:02:06AM +0106, John Ogness wrote:
> > I am not sure how to move forward. IMHO, the original plan was to push
> > this patch together with the other netconsole-related changes. In this
> > case, the conflicts will need to be solved when merging pull requests
> > from netconsole and printk trees. Well, the conflicts are trivial.
> >
> > Or I could push this patch via the printk tree and queue it for 6.19.
> > But this might be too late for netconsole.
> 
> @Breno: This new feature only exists for netconsole at the moment, so I
> am fine with it going through the netconsole tree. But we need to decide
> this soon because there are a lot of printk-changes queued for 6.19 that
> conflict with this patch and we should get those sorted out sooner
> rather than later. (Note that the patch in its current form will also
> conflict with the netconsole tree, so regardless of our decision I need
> to submit a new version.)

I would prefer you do it through the printk tree for 6.19 and I use it
in the next releae (6.20).

I do NOT have plans for integrating the port of netcon to nbcon
in 6.19, given I have other issues to solve first (described in [1] for
curious souls), and I am still a bit stuck with [2]. Given all of these
patch conflict, these patches are being a bit serial at this time.

Link: https://lore.kernel.org/all/swdpckuwwlv3uiessmtnf2jwlx3jusw6u7fpk5iggqo4t2vdws@7rpjso4gr7qp/ [1]
Link: https://lore.kernel.org/all/20251103-fix_netpoll_aa-v4-1-4cfecdf6da7c@debian.org/ [2]