From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: 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, 22 Mar 2022 09:47:29 +0100 [thread overview]
Message-ID: <YjmNIX4RsbG8LpyF@kroah.com> (raw)
In-Reply-To: <20220322083858.16887-1-fmdefrancesco@gmail.com>
On Tue, Mar 22, 2022 at 09:38:58AM +0100, 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)) {
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?
thanks,
greg k-h
next prev parent reply other threads:[~2022-03-22 9:04 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 [this message]
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
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=YjmNIX4RsbG8LpyF@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=david.kershner@unisys.com \
--cc=fmdefrancesco@gmail.com \
--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