All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Justin P. Mattock" <justinmattock@gmail.com>,
	linux-usb@vger.kernel.org, dbrownell@users.sourceforge.net,
	gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2]drivers/usb/core/sysfs.c Fix variable 'retval' set but not used
Date: Tue, 03 Aug 2010 11:13:32 -0400	[thread overview]
Message-ID: <66093.1280848412@localhost> (raw)
In-Reply-To: Your message of "Tue, 03 Aug 2010 10:29:52 EDT." <Pine.LNX.4.44L0.1008031027250.1853-100000@iolanthe.rowland.org>

[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]

On Tue, 03 Aug 2010 10:29:52 EDT, Alan Stern said:
> On Tue, 3 Aug 2010 Valdis.Kletnieks@vt.edu wrote:
> 
> > On Mon, 02 Aug 2010 21:26:28 PDT, "Justin P. Mattock" said:
> > > diff --git a/drivers/usb/core/sysfs.c b/drivers/usb/core/sysfs.c
> > 
> > >  	if (alt->string)
> > > -		retval = device_create_file(&intf->dev, &dev_attr_interface);
> > > +		device_create_file(&intf->dev, &dev_attr_interface);
> > >  	intf->sysfs_files_created = 1;
> > >  	return 0;
> 
> Justin, did you try compiling your new code?  Those unused values are 
> there because device_create_file is declared as __must_check.
> 
> > What should the code do if device_create_file() manages to fail? Yes, ignoring
> > the return value is one option, but is it the best one?  'return ret;' might be
> > another one. Somebody who understands this code and has more caffeine than me
> > should look this over.
> 
> Failure to create a file in sysfs is almost never fatal and usually not 
> even dangerous.  Ignoring the error is generally better than failing 
> the entire operation.

Then why the __must_check attribute if it's usually ignorable? I thought
that was reserved for functions that you damned sight better well check
for errors because bad things are afoot otherwise?

[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2010-08-03 15:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03  4:26 [PATCH 1/2]drivers/usb/core/sysfs.c Fix variable 'retval' set but not used Justin P. Mattock
2010-08-03  4:26 ` [PATCH 2/2]drivers/usb/host/ehci-hub.c Fix variable 'i' " Justin P. Mattock
2010-08-03 11:28 ` [PATCH 1/2]drivers/usb/core/sysfs.c Fix variable 'retval' " Valdis.Kletnieks
2010-08-03 13:30   ` Justin P. Mattock
2010-08-03 14:29   ` Alan Stern
2010-08-03 14:43     ` Justin P. Mattock
2010-08-03 15:36       ` Alan Stern
2010-08-03 16:12         ` Justin P. Mattock
2010-08-03 15:13     ` Valdis.Kletnieks [this message]
2010-08-03 15:34       ` Alan Stern
2010-08-03 15:46         ` Greg KH
2010-08-03 17:09           ` Alan Stern
2010-08-03 17:22             ` Greg KH

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=66093.1280848412@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=dbrownell@users.sourceforge.net \
    --cc=gregkh@suse.de \
    --cc=justinmattock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.