[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZtXgmi0TDfDMwnlz@hovoldconsulting.com>
Date: Mon, 2 Sep 2024 17:58:18 +0200
From: Johan Hovold <johan@...nel.org>
To: Dan Carpenter <dan.carpenter@...aro.org>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
Hans de Goede <hdegoede@...hat.com>, linux-kernel@...r.kernel.org,
platform-driver-x86@...r.kernel.org,
"Rafael J. Wysocki" <rafael@...nel.org>,
Daniel Scally <djrscally@...il.com>
Subject: Re: [PATCH v2 1/4] driver core: Ignore 0 in dev_err_probe()
On Sat, Aug 31, 2024 at 11:25:54AM +0300, Dan Carpenter wrote:
> On Thu, Aug 22, 2024 at 04:05:38PM +0300, Andy Shevchenko wrote:
> > In the similar way, ignore 0 error code (AKA "success") in
> > dev_err_probe(). This helps to simplify a code such as
> >
> > if (ret < 0)
> > return dev_err_probe(int3472->dev, ret, err_msg);
> >
> > return ret;
> >
> > to
> >
> > return dev_err_probe(int3472->dev, ret, err_msg);
> >
> > Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
>
> This is a terrible idea because currently Smatch is able to detect about one
> bug per month where someone unintentionally passes the wrong error variable
> to dev_err_probe().
>
> I really hate this.
>
> NAKed-by: Dan Carpenter <dan.carpenter@...aro.org>
Regardless of any issues this may cause for tooling, I fully agree that
this is a terrible idea that will only result in unreadable code.
return dev_err_probe(dev, ret, "registration failed\n");
Except it did not fail...
NAK
Johan
Powered by blists - more mailing lists