From: Jiri Slaby <jslaby@suse.cz>
To: Greg KH <gregkh@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
David Miller <davem@davemloft.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Mikulas Patocka <mpatocka@redhat.com>,
akpm@linux-foundation.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Jiri Slaby <jirislaby@gmail.com>
Subject: Broken link in /sys/class/net/ [was: [GIT] Networking]
Date: Sun, 30 Oct 2011 01:03:30 +0200 [thread overview]
Message-ID: <4EAC8642.3050309@suse.cz> (raw)
In-Reply-To: <20111025131315.GA1899@suse.de>
On 10/25/2011 03:13 PM, Greg KH wrote:
> On Tue, Oct 25, 2011 at 01:46:11PM +0200, Linus Torvalds wrote:
>> Anyway, after that rant about really bad practices, let me say that I
>> did fix up the conflict and I think it's right. But I won't guarantee
>> it, so please check the changes to fs/sysfs/dir.c.
>
> I think it looks ok, I've booted the merge result, and am typing and
> sending this from the new kernel, and it hasn't crashed yet :)
Hi, maybe this was not caused by the merge, but the patch[1] causes this
mess in /sys/class/net/ for me:
l????????? ? ? ? ? ? eth1
This happens after one renames a net device -- the new name is eth1 here.
[1] 4f72c0cab40 (sysfs: use rb-tree for name lookups)
regards,
--
js
suse labs
next prev parent reply other threads:[~2011-10-29 23:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 10:32 [GIT] Networking David Miller
2011-10-25 11:46 ` Linus Torvalds
2011-10-25 11:56 ` Greg KH
2011-10-25 12:03 ` Linus Torvalds
[not found] ` <m1wrbtb4rj.fsf@fess.ebiederm.org>
2011-10-25 13:12 ` Linus Torvalds
2011-10-25 13:13 ` Greg KH
2011-10-29 23:03 ` Jiri Slaby [this message]
2011-10-30 4:49 ` Broken link in /sys/class/net/ [was: [GIT] Networking] Eric W. Biederman
2011-10-30 20:49 ` Jiri Slaby
[not found] ` <m1mxcgrl7q.fsf_-_@fess.ebiederm.org>
2011-11-01 21:19 ` [PATCH] sysfs: Make sysfs_rename safe with sysfs_dirents in rbtrees Greg KH
2011-10-25 12:26 ` [GIT] Networking Linus Torvalds
2011-11-04 17:03 ` Johannes Berg
2011-11-04 17:07 ` Ben Greear
2011-11-07 11:40 ` Stanislaw Gruszka
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=4EAC8642.3050309@suse.cz \
--to=jslaby@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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).