linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH] qspinlock: no need to check return value of debugfs_create functions
Date: Wed, 23 Jan 2019 09:14:41 +0100	[thread overview]
Message-ID: <20190123081441.GE17749@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190122152151.16139-44-gregkh@linuxfoundation.org>

On Tue, Jan 22, 2019 at 04:21:43PM +0100, Greg Kroah-Hartman wrote:
> When calling debugfs functions, there is no need to ever check the
> return value.  The function can work or not, but the code logic should
> never do something different based on this.

So I've seen you do a fair number of these patches; but I don't
fully understand.

The existing code rolls back the created files such that we either have
all files or none at all. Why is this wrong?

It for some daft reason one of the debugfs calls fails (imagine this was
a module and we did modprobe while under memory pressure), why should we
present a partial interface to the 'user' ?

> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
>  kernel/locking/qspinlock_stat.h | 18 ++++--------------
>  1 file changed, 4 insertions(+), 14 deletions(-)
> 
> diff --git a/kernel/locking/qspinlock_stat.h b/kernel/locking/qspinlock_stat.h
> index 42d3d8dc8f49..766fa0c8c115 100644
> --- a/kernel/locking/qspinlock_stat.h
> +++ b/kernel/locking/qspinlock_stat.h
> @@ -213,9 +213,6 @@ static int __init init_qspinlock_stat(void)
>  	struct dentry *d_qstat = debugfs_create_dir("qlockstat", NULL);
>  	int i;
>  
> -	if (!d_qstat)
> -		goto out;
> -
>  	/*
>  	 * Create the debugfs files
>  	 *
> @@ -224,20 +221,13 @@ static int __init init_qspinlock_stat(void)
>  	 * performance.
>  	 */
>  	for (i = 0; i < qstat_num; i++)
> -		if (!debugfs_create_file(qstat_names[i], 0400, d_qstat,
> -					 (void *)(long)i, &fops_qstat))
> -			goto fail_undo;
> +		debugfs_create_file(qstat_names[i], 0400, d_qstat,
> +				    (void *)(long)i, &fops_qstat);
>  
> -	if (!debugfs_create_file(qstat_names[qstat_reset_cnts], 0200, d_qstat,
> -				 (void *)(long)qstat_reset_cnts, &fops_qstat))
> -		goto fail_undo;
> +	debugfs_create_file(qstat_names[qstat_reset_cnts], 0200, d_qstat,
> +			    (void *)(long)qstat_reset_cnts, &fops_qstat);
>  
>  	return 0;
> -fail_undo:
> -	debugfs_remove_recursive(d_qstat);
> -out:
> -	pr_warn("Could not create 'qlockstat' debugfs entries\n");
> -	return -ENOMEM;
>  }
>  fs_initcall(init_qspinlock_stat);
>  
> -- 
> 2.20.1
> 

  reply	other threads:[~2019-01-23  8:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22 15:21 [PATCH] qspinlock: no need to check return value of debugfs_create functions Greg Kroah-Hartman
2019-01-23  8:14 ` Peter Zijlstra [this message]
2019-02-01  9:12   ` Greg Kroah-Hartman
2019-01-23  9:10 ` Will Deacon
2019-01-23  9:22   ` 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=20190123081441.GE17749@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).