From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
David Kershner <david.kershner@unisys.com>,
sparmaintainer@unisys.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: unisys: Properly test debugfs_create_dir() return values
Date: Tue, 29 Mar 2022 20:46:39 +0300 [thread overview]
Message-ID: <20220329174639.GC3293@kadam> (raw)
In-Reply-To: <2030244.KlZ2vcFHjT@leap>
On Tue, Mar 29, 2022 at 07:00:49PM +0200, Fabio M. De Francesco wrote:
> On martedì 22 marzo 2022 09:38:58 CEST Fabio M. De Francesco wrote:
> > debugfs_create_dir() returns a pointers to a dentry objects. On failures
> > it returns errors. Currently the values returned to visornic_probe()
> > seem to be tested for being equal to NULL in case of failures.
> >
> > Properly test with "if (IS_ERR())" and then assign the correct error
> > value to the "err" variable.
> >
> > Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
> > ---
> > drivers/staging/unisys/visornic/visornic_main.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/staging/unisys/visornic/visornic_main.c b/drivers/staging/unisys/visornic/visornic_main.c
> > index 643432458105..58d03f3d3173 100644
> > --- a/drivers/staging/unisys/visornic/visornic_main.c
> > +++ b/drivers/staging/unisys/visornic/visornic_main.c
> > @@ -1922,11 +1922,11 @@ static int visornic_probe(struct visor_device *dev)
> > /* create debug/sysfs directories */
> > devdata->eth_debugfs_dir = debugfs_create_dir(netdev->name,
> > visornic_debugfs_dir);
> > - if (!devdata->eth_debugfs_dir) {
> > + if (IS_ERR(devdata->eth_debugfs_dir)) {
> > dev_err(&dev->device,
> > "%s debugfs_create_dir %s failed\n",
> > __func__, netdev->name);
> > - err = -ENOMEM;
> > + err = PTR_ERR(devdata->eth_debugfs_dir);
> > goto cleanup_register_netdev;
> > }
> >
> > --
> > 2.34.1
> >
> Hi Greg, Dan,
>
> Now I have time to rework this patch but, if I'm not misunderstanding, you
> asked for two contrasting works to do here...
>
> Dan wrote that "[in] this case you can delete the whole devdata->eth_debugfs_dir
> and the related code.".
>
> Greg wrote that "We really shouldn't be checking this value at all. There's
> no reason to check the return value of a debugfs_* call. Can you fix up the code to
> do that instead?".
>
> I'm confused because they look like two incompatible requests. What should I do?
Greg is saying delete the tests and the error handling. But I am
saying delete the tests, the error handling, the devdata->eth_debugfs_dir
related code and the call to debugfs_create_dir().
There is no conflict. Delete it all.
regards,
dan carpenter
prev parent reply other threads:[~2022-03-29 17:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 8:38 [PATCH] staging: unisys: Properly test debugfs_create_dir() return values Fabio M. De Francesco
2022-03-22 8:47 ` Greg Kroah-Hartman
2022-03-24 9:20 ` Fabio M. De Francesco
2022-03-22 8:48 ` Greg Kroah-Hartman
2022-03-22 8:49 ` Dan Carpenter
2022-03-22 8:55 ` Dan Carpenter
2022-03-22 9:09 ` Fabio M. De Francesco
2022-03-29 17:00 ` Fabio M. De Francesco
2022-03-29 17:46 ` Dan Carpenter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220329174639.GC3293@kadam \
--to=dan.carpenter@oracle.com \
--cc=david.kershner@unisys.com \
--cc=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sparmaintainer@unisys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox