linux-kernel - Re: [PATCH 1/2] lib/vsprintf: Add support for generic FourCCs by extending %p4cc

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

Message-ID:
 <PN3PR01MB959786A68923B2D471C129E6B8D02@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM>
Date: Wed, 12 Mar 2025 19:35:54 +0000
From: Aditya Garg <gargaditya08@...e.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
CC: Sven Peter <sven@...npeter.dev>, Thomas Zimmermann <tzimmermann@...e.de>,
	Aun-Ali Zaidi <admin@...eit.net>, Maxime Ripard <mripard@...nel.org>,
	"airlied@...hat.com" <airlied@...hat.com>, Simona Vetter <simona@...ll.ch>,
	Petr Mladek <pmladek@...e.com>, Steven Rostedt <rostedt@...dmis.org>, Rasmus
 Villemoes <linux@...musvillemoes.dk>, Sergey Senozhatsky
	<senozhatsky@...omium.org>, Jonathan Corbet <corbet@....net>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>, "apw@...onical.com"
	<apw@...onical.com>, "joe@...ches.com" <joe@...ches.com>,
	"dwaipayanray1@...il.com" <dwaipayanray1@...il.com>,
	"lukas.bulwahn@...il.com" <lukas.bulwahn@...il.com>, Linux Kernel Mailing
 List <linux-kernel@...r.kernel.org>, "dri-devel@...ts.freedesktop.org"
	<dri-devel@...ts.freedesktop.org>, "linux-doc@...r.kernel.org"
	<linux-doc@...r.kernel.org>, Hector Martin <marcan@...can.st>,
	"asahi@...ts.linux.dev" <asahi@...ts.linux.dev>
Subject: Re: [PATCH 1/2] lib/vsprintf: Add support for generic FourCCs by
 extending %p4cc



> On 13 Mar 2025, at 12:58 AM, Andy Shevchenko <andriy.shevchenko@...ux.intel.com> wrote:
> 
> On Wed, Mar 12, 2025 at 07:14:36PM +0000, Aditya Garg wrote:
>>>> On 12 Mar 2025, at 9:05 PM, Sven Peter <sven@...npeter.dev> wrote:
>>> On Wed, Mar 12, 2025, at 13:03, Aditya Garg wrote:
> 
> ...
> 
>>> I don't have a strong opinion either way: for SMC I just need to print
>>> FourCC keys for debugging / information in a few places.
>>> 
>>> I'm preparing the SMC driver for upstreaming again (after a two year delay :-()
>>> and was just going to use macros to print the SMC FourCC keys similar to
>>> DRM_MODE_FMT/DRM_MODE_ARG for now to keep the series smaller and revisit
>>> the topic later.
>>> 
>>> Right now I have these in my local tree (only compile tested so far):
>>> 
>>> #define SMC_KEY_FMT "%c%c%c%c (0x%08x)"
>>> #define SMC_KEY_ARG(k) (k)>>24, (k)>>16, (k)>>8, (k), (k)
>> 
>> That seems to be a nice alternative, which I guess Thomas was also suggesting.
> 
> I don't think it's "nice". Each of the approaches has pros and cons.

I would prefer vsprintf, but if it's not there, that remains as nice right?

> You can start from bloat-o-meter here and compare it with your %p extension.
> 
> Also, can you show the bloat-o-meter output for the vsprintf.c?

vsprintf isn't a kernel module, is it? I'll have to compile a new kernel I guess.
> 
>>> which are then used like this:
>>> 
>>>   dev_info(dev,
>>>       "Initialized (%d keys " SMC_KEY_FMT " .. " SMC_KEY_FMT ")\n",
>>>        smc->key_count, SMC_KEY_ARG(smc->first_key),
>>>        SMC_KEY_ARG(smc->last_key));
> 
> --
> With Best Regards,
> Andy Shevchenko
> 
>