[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070301.173843.104646614.davem@davemloft.net>
Date: Thu, 01 Mar 2007 17:38:43 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: shemminger@...ux-foundation.org
Cc: akpm@...ux-foundation.org, netdev@...r.kernel.org,
bugme-daemon@...zilla.kernel.org, loveminix@...oo.com.cn,
khc@...waw.pl
Subject: Re: [Bugme-new] [Bug 8107] New: dev->header_cache_update has a
random value
From: Stephen Hemminger <shemminger@...ux-foundation.org>
Date: Thu, 1 Mar 2007 15:30:25 -0800
> Your right, but so far there is no ioctl to take it out of this mode.
> So it is a one way door.
You can keep attaching a different new protocol to an HDLC
device until it is brought up.
> This device never calls hdlc->detach??
The HDLC layer calls the protocol ->detach, but the Cisco
HDLC code does not have a detach method.
I'm starting to feel that this is the bug, because as it
stands the Cisco HDLC code leaves stale pointers around
and then if you unload the Cisco HDLC module things can
explode.
-
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