From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0B2FCC433DB for ; Wed, 24 Mar 2021 19:24:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C895761A23 for ; Wed, 24 Mar 2021 19:24:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237821AbhCXTY2 (ORCPT ); Wed, 24 Mar 2021 15:24:28 -0400 Received: from smtprelay0082.hostedemail.com ([216.40.44.82]:58252 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S237667AbhCXTYP (ORCPT ); Wed, 24 Mar 2021 15:24:15 -0400 Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay06.hostedemail.com (Postfix) with ESMTP id BB3571801AC84; Wed, 24 Mar 2021 19:24:14 +0000 (UTC) X-Session-Marker: 6A6F6540706572636865732E636F6D X-HE-Tag: fish34_600c2bf2777d X-Filterd-Recvd-Size: 4692 Received: from [192.168.1.159] (unknown [47.151.137.21]) (Authenticated sender: joe@perches.com) by omf02.hostedemail.com (Postfix) with ESMTPA; Wed, 24 Mar 2021 19:24:11 +0000 (UTC) Message-ID: Subject: Re: [RFC patch] vsprintf: Allow %pe to print non PTR_ERR %pe uses as decimal From: Joe Perches To: Rasmus Villemoes , Arnd Bergmann , Petr Mladek , Steven Rostedt , Sergey Senozhatsky , Andy Shevchenko Cc: Philipp Zabel , David Airlie , Daniel Vetter , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , NXP Linux Team , Marco Felsch , Laurent Pinchart , Liu Ying , dri-devel , Linux ARM , Linux Kernel Mailing List Date: Wed, 24 Mar 2021 12:24:10 -0700 In-Reply-To: <9feab1e8-4dee-6b79-03f7-7b9f0cb24f6e@rasmusvillemoes.dk> References: <20210324121832.3714570-1-arnd@kernel.org> <810d36184b9fa2880d3ba7738a8f182e27f5107b.camel@perches.com> <3252fd83141aa9e0e6001acee1dd98e87c676b9a.camel@perches.com> <9feab1e8-4dee-6b79-03f7-7b9f0cb24f6e@rasmusvillemoes.dk> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.1-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2021-03-24 at 18:33 +0100, Rasmus Villemoes wrote: > On 24/03/2021 18.20, Joe Perches wrote: > > On Wed, 2021-03-24 at 09:52 -0700, Joe Perches wrote: > > > On Wed, 2021-03-24 at 17:42 +0100, Arnd Bergmann wrote: > > > > On Wed, Mar 24, 2021 at 3:20 PM Joe Perches wrote: > > > [] > > > > > > diff --git a/drivers/gpu/drm/imx/imx-ldb.c b/drivers/gpu/drm/imx/imx-ldb.c > > > > > [] > > > > > > @@ -197,6 +197,12 @@ static void imx_ldb_encoder_enable(struct drm_encoder *encoder) > > > > > >       int dual = ldb->ldb_ctrl & LDB_SPLIT_MODE_EN; > > > > > >       int mux = drm_of_encoder_active_port_id(imx_ldb_ch->child, encoder); > > > > > > > > > > > > + if (mux < 0 || mux >= ARRAY_SIZE(ldb->clk_sel)) { > > > > > > + dev_warn(ldb->dev, "%s: invalid mux %d\n", > > > > > > + __func__, ERR_PTR(mux)); > > > > > > > > > > This does not compile without warnings. > > > > > > > > > > drivers/gpu/drm/imx/imx-ldb.c: In function ‘imx_ldb_encoder_enable’: > > > > > drivers/gpu/drm/imx/imx-ldb.c:201:22: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘void *’ [-Wformat=] > > > > >   201 | dev_warn(ldb->dev, "%s: invalid mux %d\n", > > > > >       | ^~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > > > If you want to use ERR_PTR, the %d should be %pe as ERR_PTR > > > > > is converting an int a void * to decode the error type and > > > > > emit it as a string. > > > > > > > > Sorry about that. > > > > > > > > I decided against using ERR_PTR() in order to also check for > > > > positive array overflow, but the version I tested was different from > > > > the version I sent. > > > > > > > > v3 coming. > > > > > > Thanks. No worries. > > > > > > Up to you, vsprintf would emit the positive mux as a funky hashed > > > hex value by default if you use ERR_PTR with mux > ARRAY_SIZE so > > > perhaps %d without the ERR_PTR use makes the most sense. > > > > > > > > Maybe it's better to output non PTR_ERR %pe uses as decimal so this > > sort of code would work. > > No, because that would leak the pointer value when somebody has > accidentally passed a real kernel pointer to %pe. I think it's not really an issue. _All_ code that uses %p extensions need inspection anyway. It's already possible to intentionally 'leak' the ptr value by using %pe, -ptr so I think that's not really an issue. > > If the code wants a cute -EFOO string explaining what's wrong, what > about "%pe", ERR_PTR(mux < 0 : mux : -ERANGE)? Or two separate error > messages > > if (mux < 0) >   ... > else if (mux >= ARRAY_SIZE()) >   ... Multiple tests, more unnecessary code, multiple format strings, etc...