[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250919165438.GB589507@horms.kernel.org>
Date: Fri, 19 Sep 2025 17:54:38 +0100
From: Simon Horman <horms@...nel.org>
To: Tariq Toukan <tariqt@...dia.com>
Cc: Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Saeed Mahameed <saeedm@...dia.com>,
Leon Romanovsky <leon@...nel.org>, Mark Bloch <mbloch@...dia.com>,
Julia Lawall <Julia.Lawall@...ia.fr>,
Nicolas Palix <nicolas.palix@...g.fr>,
Richard Cochran <richardcochran@...il.com>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-rdma@...r.kernel.org, cocci@...ia.fr,
Gal Pressman <gal@...dia.com>
Subject: Re: [PATCH net-next 1/2] scripts/coccinelle: Find PTR_ERR() to %pe
candidates
On Thu, Sep 18, 2025 at 01:43:46PM +0300, Tariq Toukan wrote:
> From: Gal Pressman <gal@...dia.com>
>
> Add a new Coccinelle script to identify places where PTR_ERR() is used
> in print functions and suggest using the %pe format specifier instead.
>
> For printing error pointers (i.e., a pointer for which IS_ERR() is true)
> %pe will print a symbolic error name (e.g,. -EINVAL), opposed to the raw
> errno (e.g,. -22) produced by PTR_ERR().
> It also makes the code cleaner by saving a redundant call to PTR_ERR().
>
> The script supports context, report, and org modes.
>
> Example transformation:
> printk("Error: %ld\n", PTR_ERR(ptr)); // Before
> printk("Error: %pe\n", ptr); // After
>
> Signed-off-by: Gal Pressman <gal@...dia.com>
> Reviewed-by: Alexei Lazar <alazar@...dia.com>
> Signed-off-by: Tariq Toukan <tariqt@...dia.com>
Thanks, having this check seems very nice to me.
Reviewed-by: Simon Horman <horms@...nel.org>
Powered by blists - more mailing lists