From: David Miller <davem@davemloft.net>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, jgarzik@pobox.com
Subject: Re: [bug, 2.6.24-rc1] sysfs: duplicate filename 'eth0' can not be created
Date: Mon, 29 Oct 2007 15:36:27 -0700 (PDT) [thread overview]
Message-ID: <20071029.153627.04824774.davem@davemloft.net> (raw)
In-Reply-To: <20071029211746.GA19876@elte.hu>
From: Ingo Molnar <mingo@elte.hu>
Date: Mon, 29 Oct 2007 22:17:46 +0100
>
> hm, this seems to have popped up in the last few days, never had it
> before:
>
> sysfs: duplicate filename 'eth0' can not be created
> WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
I checked in a change from Stephen Hemminger last week which
should keep this case from emitting warning messages.
commit c8d90dca3211966ba5189e0f3d4bccd558d9ae08
Author: Stephen Hemminger <shemminger@linux-foundation.org>
Date: Fri Oct 26 03:53:42 2007 -0700
[NET] dev_change_name: ignore changes to same name
Prevent error/backtrace from dev_rename() when changing
name of network device to the same name. This is a common
situation with udev and other scripts that bind addr to device.
Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
diff --git a/net/core/dev.c b/net/core/dev.c
index f1647d7..ddfef3b 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -883,6 +883,9 @@ int dev_change_name(struct net_device *dev, char *newname)
if (!dev_valid_name(newname))
return -EINVAL;
+ if (strncmp(newname, dev->name, IFNAMSIZ) == 0)
+ return 0;
+
memcpy(oldname, dev->name, IFNAMSIZ);
if (strchr(newname, '%')) {
prev parent reply other threads:[~2007-10-29 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 21:17 [bug, 2.6.24-rc1] sysfs: duplicate filename 'eth0' can not be created Ingo Molnar
2007-10-29 21:35 ` Jeff Garzik
2007-10-29 21:49 ` Rick Jones
2007-10-29 21:40 ` Stephen Hemminger
2007-10-29 21:48 ` Ingo Molnar
2007-10-29 22:36 ` David Miller [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=20071029.153627.04824774.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).