All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <larry.finger@lwfinger.net>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: David Miller <davem@davemloft.net>, linux-kernel@vger.kernel.org
Subject: Re: Error message from device_rename in drivers/base/core.c
Date: Wed, 08 Aug 2007 07:23:34 -0500	[thread overview]
Message-ID: <46B9B5C6.2070100@lwfinger.net> (raw)
In-Reply-To: <20070808113359.71e77f49@gondolin.boeblingen.de.ibm.com>

Cornelia Huck wrote:
> On Tue, 07 Aug 2007 21:37:24 -0700 (PDT),
> David Miller <davem@davemloft.net> wrote:
> 
>> I think this check belongs in udev not in the kernel.  Thankfully
>> this message at least tells us it is happening, please don't
>> remove it.
> 
> Hm, device_rename() could alternatively just return success if
> dev->bus_id and new_name are the same.

That is what my proposed patch did. One could argue that the test should come before the failure, 
not after, but the effect is the same.

>> I'm pretty sure it's UDEV doing this, and it should not try to rename
>> a netdevice to what it already is named.
> 
> But it shouldn't cause an error either :)

I agree with you, but you and David can fight it out. While finding out where to ask/complain about 
udev, I had a private communication with GregKH. He thinks that a patch to fix this has already been 
pushed through Linus. As Linville's wireless-dev tree is a little behind, I'm waiting to see if it 
gets fixed here by 2.6.23-rc3. If not, I'll talk to the udev/hotplug folks.

  reply	other threads:[~2007-08-08 12:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08  4:17 Error message from device_rename in drivers/base/core.c Larry Finger
2007-08-08  4:37 ` David Miller
2007-08-08  4:52   ` Larry Finger
2007-08-08  4:55     ` David Miller
2007-08-08  5:02       ` Larry Finger
2007-08-08  6:18     ` Sam Ravnborg
2007-08-08  9:33   ` Cornelia Huck
2007-08-08 12:23     ` Larry Finger [this message]
2007-08-08 13:46       ` Kay Sievers
2007-08-08 13:59         ` Larry Finger
2007-08-08 14:14           ` Kay Sievers
2007-08-08 15:19             ` Larry Finger

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=46B9B5C6.2070100@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=cornelia.huck@de.ibm.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.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 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.