From: Greg KH <gregkh@linuxfoundation.org>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
jic23@kernel.org,
Michael Hennerich <michael.hennerich@analog.com>
Subject: Re: [PATCH] iio: core: print error message on debugfs register failure
Date: Tue, 17 Dec 2019 16:19:40 +0100 [thread overview]
Message-ID: <20191217151940.GB3654493@kroah.com> (raw)
In-Reply-To: <20191211151636.13547-1-alexandru.ardelean@analog.com>
On Wed, Dec 11, 2019 at 05:16:36PM +0200, Alexandru Ardelean wrote:
> From: Michael Hennerich <michael.hennerich@analog.com>
>
> If there's a failure when registering a debugfs entry for a device, don't
> silently ignore the failure. Instead, print an error message and an error
> code signaling the failure.
No, never do that.
> Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
> Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
> ---
> drivers/iio/industrialio-core.c | 34 +++++++++++++++++++++++++++------
> 1 file changed, 28 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/iio/industrialio-core.c b/drivers/iio/industrialio-core.c
> index dab67cb69fe6..662dabf8b08c 100644
> --- a/drivers/iio/industrialio-core.c
> +++ b/drivers/iio/industrialio-core.c
> @@ -364,23 +364,45 @@ static const struct file_operations iio_debugfs_reg_fops = {
> static void iio_device_unregister_debugfs(struct iio_dev *indio_dev)
> {
> debugfs_remove_recursive(indio_dev->debugfs_dentry);
> + indio_dev->debugfs_dentry = NULL;
> }
>
> static void iio_device_register_debugfs(struct iio_dev *indio_dev)
> {
> + struct dentry *d;
> + int ret;
> +
> if (indio_dev->info->debugfs_reg_access == NULL)
> return;
>
> if (!iio_debugfs_dentry)
> return;
>
> - indio_dev->debugfs_dentry =
> - debugfs_create_dir(dev_name(&indio_dev->dev),
> - iio_debugfs_dentry);
> + d = debugfs_create_dir(dev_name(&indio_dev->dev), iio_debugfs_dentry);
> + if (IS_ERR_OR_NULL(d))
> + goto error;
No, don't do that, I spent a lot of time removing all of these pointless
checks.
No kernel code shoudl ever care if debugfs is workign or not, just make
the call and move on. You can always pass the result of a debugfs call
into another one with no problems.
> +
> + indio_dev->debugfs_dentry = d;
> +
> + d = debugfs_create_file("direct_reg_access", 0644,
> + indio_dev->debugfs_dentry, indio_dev,
> + &iio_debugfs_reg_fops);
> +
> + if (IS_ERR_OR_NULL(d))
> + goto error;
This check isn't even correct :)
So this isn't going to work no matter what, sorry.
just don't do this.
The code is just fine as-is.
thanks,
greg k-h
next prev parent reply other threads:[~2019-12-17 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 15:16 Alexandru Ardelean
2019-12-17 15:19 ` Greg KH [this message]
2019-12-17 15:23 ` Ardelean, Alexandru
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=20191217151940.GB3654493@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexandru.ardelean@analog.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.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
all inboxes | Powered by JetHome®