From: Larry Finger <larry.finger@lwfinger.net>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
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 10:19:22 -0500 [thread overview]
Message-ID: <46B9DEFA.1070300@lwfinger.net> (raw)
In-Reply-To: <1186582491.2573.17.camel@lov.localdomain>
Kay Sievers wrote:
> On Wed, 2007-08-08 at 08:59 -0500, Larry Finger wrote:
>> Kay Sievers wrote:
>>> On 8/8/07, Larry Finger <larry.finger@lwfinger.net> wrote:
>>>> 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.
>>> Hmm, I can not immediately see how udev could request the renaming to
>>> the same name:
>>>
>>> /* look if we want to change the name of the netif */
>>> if (strcmp(udev->name, udev->dev->kernel) != 0) {
>>> ...
>>> retval = rename_netif(udev);
>>> ...
>>> }
>>>
>>> What udev version is it and which distro and version?
>> My distro is openSUSE 10.2, which is fully patched/updated. According to YaST, I'm using version
>> 103-12 x86_64. My kernel is 2.6.23-rc2 from John Linville's git tree - I run bcm43xx-mac80211.
>
> Oh, that's likely a bug in the SUSE versions of the persistent net
> interface rules. It is calling ifrename when it needs to swap interface
> names (temp rename to free the target name), that logic which may have
> that bug.
> For the next SUSE release, it is replaced by the (now available)
> upstream stuff from the udev tree, which most distros use now, and which
> should not have that problem.
Thanks for the explanation. I'll ignore the message - it doesn't cause any problems anyway, and I'll
expect it to go away when openSUSE 10.3 comes out in October. I think I'll post a bug report with
SUSE just to make sure it gets fixed.
Larry
prev parent reply other threads:[~2007-08-08 15:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 4:17 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
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 [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=46B9DEFA.1070300@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=cornelia.huck@de.ibm.com \
--cc=davem@davemloft.net \
--cc=kay.sievers@vrfy.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®