Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: Devendra Naga
	<devendra.aaru-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] arm: mach-tegra: check wether we have debugfs enabled or not
Date: Wed, 17 Oct 2012 23:14:12 +0100	[thread overview]
Message-ID: <20121017221412.GO21164@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <507F2185.3070408-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

On Wed, Oct 17, 2012 at 03:22:13PM -0600, Stephen Warren wrote:
> On 10/17/2012 02:12 PM, Russell King - ARM Linux wrote:
> > On Wed, Oct 17, 2012 at 03:13:16PM -0400, Devendra Naga wrote:
> >> if debugfs is not enabled in kernel it returns -ENODEV, check it
> >> with IS_ERR_OR_NULL along with the null return if it fails to
> >> create a file in debugfs.
> >>
> >> Signed-off-by: Devendra Naga <devendra.aaru-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> >> ---
> >>  arch/arm/mach-tegra/powergate.c |    2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/arch/arm/mach-tegra/powergate.c b/arch/arm/mach-tegra/powergate.c
> >> index de0662d..1809b91d 100644
> >> --- a/arch/arm/mach-tegra/powergate.c
> >> +++ b/arch/arm/mach-tegra/powergate.c
> >> @@ -269,7 +269,7 @@ int __init tegra_powergate_debugfs_init(void)
> >>  	if (powergate_name) {
> >>  		d = debugfs_create_file("powergate", S_IRUGO, NULL, NULL,
> >>  			&powergate_fops);
> >> -		if (!d)
> >> +		if (IS_ERR_OR_NULL(d))
> >>  			return -ENOMEM;
> > 
> > So, you want to make this function hard-fail if a debugfs error occurs
> > _or_ debugfs is not configured?  That doesn't seem to be a clever thing
> > to do.
> 
> In practice, that quoted chunk of code is inside an #ifdef
> CONFIG_DEBUG_FS, so according to the documentation for
> debugfs_create_file(), the IS_ERR case of IS_ERR_OR_NULL cannot happen
> here. So, the above change is a no-op, so there's not much point
> applying it.

Ok.  Another reason not to apply it is that should the ifdefs get
removed, it'll start failing when debugfs is disabled with -ENOMEM,
which isn't bright.  A further reason is it's another place that'd
need reviewing for bad usage of the IS_ERR_OR_NULL() problem I've
pointed out this evening.

      parent reply	other threads:[~2012-10-17 22:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17 19:13 [PATCH] arm: mach-tegra: check wether we have debugfs enabled or not Devendra Naga
     [not found] ` <1350501196-5632-1-git-send-email-devendra.aaru-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-10-17 20:12   ` Russell King - ARM Linux
     [not found]     ` <20121017201244.GN21164-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2012-10-17 20:18       ` devendra.aaru
2012-10-17 21:22       ` Stephen Warren
     [not found]         ` <507F2185.3070408-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-10-17 22:14           ` Russell King - ARM Linux [this message]

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=20121017221412.GO21164@n2100.arm.linux.org.uk \
    --to=linux-lfz/pmaqli7xmaaqvzeohq@public.gmane.org \
    --cc=devendra.aaru-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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