From: Frederic Barrat <fbarrat@linux.ibm.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Andrew Donnellan <ajd@linux.ibm.com>
Subject: Re: [PATCH] cxl: no need to check return value of debugfs_create functions
Date: Wed, 12 Jun 2019 16:10:33 +0200 [thread overview]
Message-ID: <e887909b-00d4-c6d9-2bda-677ad2685f64@linux.ibm.com> (raw)
In-Reply-To: <20190612100226.GA18368@kroah.com>
Le 12/06/2019 à 12:02, Greg Kroah-Hartman a écrit :
> On Wed, Jun 12, 2019 at 11:51:21AM +0200, Arnd Bergmann wrote:
>> On Tue, Jun 11, 2019 at 8:13 PM Greg Kroah-Hartman
>> <gregkh@linuxfoundation.org> wrote:
>>
>>> @@ -64,8 +64,6 @@ int cxl_debugfs_adapter_add(struct cxl *adapter)
>>>
>>> snprintf(buf, 32, "card%i", adapter->adapter_num);
>>> dir = debugfs_create_dir(buf, cxl_debugfs);
>>> - if (IS_ERR(dir))
>>> - return PTR_ERR(dir);
>>> adapter->debugfs = dir;
>>>
>>
>> Should the check for 'cxl_debugfs' get removed here as well?
>
> Maybe, I could not determine the logic if those functions could be
> called before cxl_debugfs was ever set.
>
> And debugfs_create_dir() will not return a NULL value if an error
> happens, so no need to worry about files being created in the wrong
> place.
>
>> If that is null, we might put the subdir in the wrong place in the
>> tree, but that would otherwise be harmless as well, and the
>> same thing happens if 'dir' is NULL above and we add the
>> files in the debugfs root later (losing the ability to clean up
>> afterwards).
>>
>> int cxl_debugfs_adapter_add(struct cxl *adapter)
>> {
>> struct dentry *dir;
>> char buf[32];
>>
>> if (!cxl_debugfs)
>> return -ENODEV;
>>
>> It's still a bit odd to return an error, since the caller then just
>> ignores the return code anway:
>
> Then let's just return nothing.
>
>> /* Don't care if this one fails: */
>> cxl_debugfs_adapter_add(adapter);
>>
>> It would seem best to change the return type to 'void' here for
>> consistency.
>
> I agree, let me go do that.
I don't see any problems with turning all those function return types to
'void'. Thanks for pointing it out and the clean up!
Fred
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2019-06-12 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 18:13 [PATCH] cxl: no need to check return value of debugfs_create functions Greg Kroah-Hartman
2019-06-12 9:51 ` Arnd Bergmann
2019-06-12 10:02 ` Greg Kroah-Hartman
2019-06-12 14:10 ` Frederic Barrat [this message]
2019-06-12 15:54 ` Greg Kroah-Hartman
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=e887909b-00d4-c6d9-2bda-677ad2685f64@linux.ibm.com \
--to=fbarrat@linux.ibm.com \
--cc=ajd@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).