From: lkml20100708@newton.leun.net
To: David Miller <davem@davemloft.net>
Cc: ebiederm@xmission.com, greg@kroah.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, adobriyan@gmail.com,
kaber@trash.net
Subject: Re: NET_NS: unregister_netdevice: waiting for lo to become free (adding ipv6 address to interface)
Date: Fri, 6 Aug 2010 01:45:26 +0200 [thread overview]
Message-ID: <20100806014526.42ffda09@xenia.leun.net> (raw)
In-Reply-To: <20100805.131128.42817872.davem@davemloft.net>
On Thu, 05 Aug 2010 13:11:28 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: ebiederm@xmission.com (Eric W. Biederman)
> Date: Thu, 05 Aug 2010 12:57:59 -0700
>
> > I wonder what has changed with ipv6 recently.
>
> There was a recent fix to the IGMP snooping code we have in
> the bridging layer, if parsing of an ipv6 IGMP packet failed
> we'd leak the packet (and thus references to whatever device
> it referenced).
>
> commit 6d1d1d398cb7db7a12c5d652d50f85355345234f
[...]
But this patch is not in 2.6.35 and therefore cannot make the
difference Eric sees (belives to see) between his modified 2.6.32 and
2.6.35.
Also, this patch, if I understand that correctly, only changes bridging
and in my scenario bridge.ko (have it as module) was not even loaded,
so applying this patch should not make any difference for the bug I
see, or do I overlook something?
So, I guess, your answer was general information to Erics question what
changed with ipv6, not related to that bug we seek in particular?
--
MfG,
Michael Leun
next prev parent reply other threads:[~2010-08-05 23:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <loom.20100708T183152-326@post.gmane.org>
[not found] ` <20100709235744.GA12752@kroah.com>
[not found] ` <20100710101540.2799c9ef@xenia.leun.net>
[not found] ` <20100710140800.GA20424@kroah.com>
[not found] ` <20100710165208.59272ae6@xenia.leun.net>
[not found] ` <20100710235323.5336f627@xenia.leun.net>
2010-07-11 17:29 ` FW: NET_NS: unregister_netdevice: waiting for lo to become free (after using openvpn) (was Re: sysfs bug when using tun with network namespaces) Michael Leun
2010-08-04 13:35 ` Michael Leun
2010-08-04 21:46 ` Greg KH
2010-08-04 22:04 ` NET_NS: unregister_netdevice: waiting for lo to become free (after using openvpn) Eric W. Biederman
2010-08-04 22:11 ` NET_NS: unregister_netdevice: waiting for lo to become free (after using openvpn) (was Re: sysfs bug when using tun with network namespaces) Michael Leun
2010-08-05 0:12 ` Eric W. Biederman
2010-08-05 9:25 ` Michael Leun
2010-08-05 9:51 ` NET_NS: unregister_netdevice: waiting for lo to become free (after using openvpn) Eric W. Biederman
2010-08-05 10:13 ` Michael Leun
2010-08-05 11:47 ` NET_NS: unregister_netdevice: waiting for lo to become free (adding ipv6 address to interface) Michael Leun
2010-08-05 19:57 ` Eric W. Biederman
2010-08-05 20:11 ` David Miller
2010-08-05 23:45 ` lkml20100708 [this message]
2010-08-06 0:09 ` Michael Leun
2010-10-21 15:15 ` Michael Leun
2010-10-22 12:48 ` David Lamparter
2010-10-22 17:05 ` Michael Leun
2010-10-24 13:15 ` Michael Leun
2010-12-06 16:08 ` Menil Jean-Philippe
2010-12-06 21:22 ` Eric W. Biederman
2010-12-06 22:47 ` Michael Leun
2010-12-07 10:40 ` Menil Jean-Philippe
2010-08-05 16:57 ` NET_NS: unregister_netdevice: waiting for lo to become free (after using openvpn) Ben Greear
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=20100806014526.42ffda09@xenia.leun.net \
--to=lkml20100708@newton.leun.net \
--cc=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=greg@kroah.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).