[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1275504953.3915.31.camel@jlt3.sipsolutions.net>
Date: Wed, 02 Jun 2010 20:55:53 +0200
From: Johannes Berg <johannes@...solutions.net>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Greg KH <greg@...ah.com>, netdev <netdev@...r.kernel.org>
Subject: Re: sysfs class/net/ problem
On Wed, 2010-06-02 at 11:05 -0700, Eric W. Biederman wrote:
> If you want to dig into this look at sysfs_delete_link. instrument
> it so that you can see if it is called for wlan{0,1,2} and see what
> ns it is called for.
>
> My current hypothesis is something is causing us to try and delete
> the symlink from the wrong namespace, so we just skip that part of it.
[ 78.253128] create link wlan0 ns=ffff88001ce1e600
...
[ 93.462268] delete link wlan0 ns=ffff88001ce1e600
looks the same ...
Also note
[ 109.872488] netconsole: network logging stopped, interface wlan0 unregistered
[ 109.872910] PM: Removing info for No Bus:wlan0
[ 109.872941] delete link wlan0 ns=ffff88001e9bd600
[ 110.130563] PM: Removing info for No Bus:rfkill0
[ 110.130599] delete link rfkill0 ns=ffff88001b61ea80
[ 110.131135] PM: Removing info for No Bus:phy0
[ 110.131161] delete link phy0 ns=ffff88001b61e240
[ 110.131424] PM: Removing info for No Bus:hwsimdev0
[ 110.131445] delete link hwsimdev0 ns=ffff88001b67ed80
(I changed the struct device thing in hwsim to be hwsimdev%d rather than
hwsim%d to tell the difference to hwsim0, the monitor netdev) so it's
getting removed from PM way after the wlan0 that links into it...
johannes
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists