[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m11w4lho08.fsf@frodo.ebiederm.org>
Date: Thu, 01 May 2008 11:34:31 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: "Serge E. Hallyn" <serue@...ibm.com>
Cc: Greg KH <gregkh@...e.de>, Benjamin Thery <benjamin.thery@...l.net>,
linux-kernel@...r.kernel.org, Al Viro <viro@....linux.org.uk>,
Tejun Heo <htejun@...il.com>,
Daniel Lezcano <dlezcano@...ibm.com>,
Pavel Emelyanov <xemul@...nvz.org>, netdev@...r.kernel.org
Subject: Re: [PATCH 00/10] sysfs tagged directories
"Serge E. Hallyn" <serue@...ibm.com> writes:
> Quoting Greg KH (gregkh@...e.de):
> Now before moving veth1 to the new netns, we have in the container:
> /sys/class/net:
> lo sit0
>
> /sys/devices/virtual/net:
> lo sit0
>
> and after moving veth1, we have in the container:
>
> /sys/class/net:
> lo sit0 veth1
>
> /sys/devices/virtual/net:
> lo sit0
>
> In the parent network namespace, veth1 is removed from /sys/class/net
> but remains in /sys/devices/virtual/net.
The symlink is gone by the real directory remains?
> I'm not sure whether this is the renaming bug that Daniel Lezcano's
> patch addresses. If not (as I suspect) then that clearly needs to be
> fixed.
>
> Benjamin can you play around with this and test it with Daniel's
> patch?
Darn. It appears we have a regression in this patchset.
That part used to work.
I was thinking of blaming sysfs_rename_link. But it the
links are fine so it looks more likely that sysfs has morphed once
again and we have a reference counting issue or something similar.
Yuck. d_move and the other moves should have worked.
>From a purely get the good less controversial parts of this
patchset in. I suggest we look at patches 7/10 and 8/10 (without
the tag_ops). And introduce and start using sysfs_delete_link
and sysfs_rename_link. That code seems pretty stable and is
generally a code reduction all by itself by reducing a common
idiom into a single function.
Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists