linux-kernel - Re: [PATCH] printk: Increase PRINTK_PREFIX_MAX and the buf size in print

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-next>] [day] [month] [year] [list]

Date: Mon, 3 Jun 2024 14:42:44 +0200
From: Petr Mladek <pmladek@...e.com>
To: "gxxa03070307@...il.com" <gxxa03070307@...il.com>
Cc: "john.ogness" <john.ogness@...utronix.de>,
	rostedt <rostedt@...dmis.org>,
	senozhatsky <senozhatsky@...omium.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	fengqi <fengqi@...omi.com>,
	高翔 <gaoxiang19870307@....com>
Subject: Re: [PATCH] printk: Increase PRINTK_PREFIX_MAX and the buf size in
 print_caller.

On Mon 2024-06-03 16:47:01, gxxa03070307@...il.com wrote:
> I need to populate the temporary variable "caller" in "print_caller" func with the additional information. And it's no use defining a buf in out-of-tree patch.
> In out-of-tree patch, I can only add hooks (special cases), I can't change anything else, because it needs to be consistent with mainline linux.
> caller buf in mainline linux is it better to make the buf bigger and leave some space?

I do not understand. Why the buffer size has to be consistent with
mainline linux?

Really, it does not make much sense to upstream just this part
of your out-of-tree patch?

Best Regards,
Petr