From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Osama Muhammad <osmtendev@gmail.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] smsdvb-debugfs.c: Fix error checking for debugfs_create_file
Date: Fri, 26 May 2023 11:53:40 +0100 [thread overview]
Message-ID: <20230526115340.295b1122@sal.lan> (raw)
In-Reply-To: <20230524164210.20567-1-osmtendev@gmail.com>
Em Wed, 24 May 2023 21:42:10 +0500
Osama Muhammad <osmtendev@gmail.com> escreveu:
> This patch fixes the error checking in smsdvb-debugfs.c in
> debugfs_create_file. The correct way to check if an error occurred
> is using 'IS_ERR_OR_NULL' inline function.
>
> Signed-off-by: Osama Muhammad <osmtendev@gmail.com>
> ---
> drivers/media/common/siano/smsdvb-debugfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/common/siano/smsdvb-debugfs.c b/drivers/media/common/siano/smsdvb-debugfs.c
> index 8916bb644756..0f8750d7993c 100644
> --- a/drivers/media/common/siano/smsdvb-debugfs.c
> +++ b/drivers/media/common/siano/smsdvb-debugfs.c
> @@ -469,7 +469,7 @@ int smsdvb_debugfs_create(struct smsdvb_client_t *client)
>
> d = debugfs_create_file("stats", S_IRUGO | S_IWUSR, client->debugfs,
> client, &debugfs_stats_ops);
> - if (!d) {
> + if (IS_ERR_OR_NULL(d)) {
> debugfs_remove(client->debugfs);
> return -ENOMEM;
if IS_ERR, it is probably better to return PTR_ERR(d).
So, please change it accordingly, returning -ENOMEM only on NULL, e. g.
something like (untested):
if (IS_ERR_OR_NULL(d)) {
debugfs_remove(client->debugfs);
if (!d)
return -ENOMEM;
return PTR_ERR(d);
}
Regards,
Mauro
next prev parent reply other threads:[~2023-05-26 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 16:42 [PATCH] smsdvb-debugfs.c: Fix error checking for debugfs_create_file Osama Muhammad
2023-05-26 10:53 ` Mauro Carvalho Chehab [this message]
2023-05-28 15:12 ` Osama Muhammad
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=20230526115340.295b1122@sal.lan \
--to=mchehab@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=osmtendev@gmail.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