From: Jiri Slaby <jslaby@suse•cz>
To: Kay Sievers <kay.sievers@vrfy•org>
Cc: "Eric W. Biederman" <ebiederm@xmission•com>,
Greg KH <greg@kroah•com>, LKML <linux-kernel@vger•kernel.org>,
ML netdev <netdev@vger•kernel.org>
Subject: network regression: cannot rename netdev twice
Date: Tue, 31 Jan 2012 11:41:19 +0100 [thread overview]
Message-ID: <4F27C54F.1010107@suse.cz> (raw)
In-Reply-To: <CAPXgP12Sr2KzGJ9RA13QBOCkctb-z3O4+1uHOjANgMDDv2pxaQ@mail.gmail.com>
On 01/30/2012 11:52 PM, Kay Sievers wrote:
> 2012/1/30 Jiri Slaby <jslaby@suse•cz>:
>> I cannot boot properly with this commit:
>> commit 524b6c5b39b931311dfe5a2f5abae2f5c9731676
>> Author: Eric W. Biederman <ebiederm@xmission•com>
>> Date: Sun Dec 18 20:09:31 2011 -0800
>>
>> sysfs: Kill nlink counting.
>>
>>
>> 1) network systemd rule doesn't start network
>
> What does that mean? What's a network systemd rule?
Oh, perhaps you call it a service file, not rule file?
Anyway this is a different bug. Revert of the patch above does not help.
The bug lays in the network layer. udev is unable to perform persistent
eth naming:
# ip link set eth0 name eth1 -- this one is OK
# ip link set eth1 name eth0
RTNETLINK answers: No such file or directory
thanks,
--
js
suse labs
next parent reply other threads:[~2012-01-31 10:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F27120A.4040106@suse.cz>
[not found] ` <CAPXgP12Sr2KzGJ9RA13QBOCkctb-z3O4+1uHOjANgMDDv2pxaQ@mail.gmail.com>
2012-01-31 10:41 ` Jiri Slaby [this message]
2012-01-31 10:52 ` network regression: cannot rename netdev twice Kay Sievers
2012-01-31 11:00 ` Jiri Slaby
2012-01-31 11:13 ` Kay Sievers
2012-01-31 11:17 ` Jiri Slaby
2012-01-31 11:58 ` Kay Sievers
2012-01-31 14:18 ` Eric W. Biederman
2012-01-31 14:40 ` [PATCH] sysfs: Update the name hash when renaming sysfs entries Eric W. Biederman
2012-01-31 14:41 ` Jiri Slaby
2012-01-31 14:55 ` Greg KH
2012-02-04 2:14 ` network regression: cannot rename netdev twice Henrique de Moraes Holschuh
2012-02-06 20:03 ` Kay Sievers
2012-02-08 2:00 ` Henrique de Moraes Holschuh
2012-02-08 3:50 ` Kay Sievers
2012-02-08 6:42 ` Valdis.Kletnieks
2012-02-08 10:57 ` Kay Sievers
2012-02-08 20:06 ` Valdis.Kletnieks
2012-02-08 20:27 ` Stephen Hemminger
2012-02-08 23:48 ` Kay Sievers
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=4F27C54F.1010107@suse.cz \
--to=jslaby@suse$(echo .)cz \
--cc=ebiederm@xmission$(echo .)com \
--cc=greg@kroah$(echo .)com \
--cc=kay.sievers@vrfy$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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