Re: [PATCH 2/3] sysfs: remove error messages for -EEXIST case

From: Greg KH
Date: Wed May 14 2008 - 23:15:41 EST


On Wed, May 14, 2008 at 06:26:37PM -0700, David Miller wrote:
> From: Stephen Hemminger <shemminger@xxxxxxxxxx>
> Date: Wed, 14 May 2008 18:16:03 -0700
>
> > It is possible that the entry in sysfs already exists, one case of this is
> > when a network device is renamed to bonding_masters. Anyway, in this case
> > the proper error path is for device_rename to return an error code, not to
> > generate bogus backtrace and errors.
> >
> > Also, to avoid possible races, the create link should be done before the
> > remove link. This makes a device rename atomic operation like other renames.
> >
> > Signed-off-by: Stephen Hemminger <shemminger@xxxxxxxxxx>
>
> I definitely agree with this change.
>
> We have several cases where device names are user configurable,
> yet the devices live in a directory which also has subdirectories
> created by other subsystems.
>
> It's pointless to require the top-level guy to look for any
> purge out any subdirectory cases, that's none of it's business.
>
> I realize the backtrace is useful for finding bugs, but in this
> case it's definitely not appropriate.

Fair enough, I have no objection to these.

David, do you want me to take them through my tree? Or are they
dependant on the network core changes as well? If so, I have no
problem you taking them. Feel free to add a:
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxx>
to them in that case.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/