From: Ben Greear <greearb@candelatech.com>
To: Andre Tomt <andre@tomt.net>
Cc: netdev@oss.sgi.com
Subject: Re: 2.6.10 ipv6/8021q lockup on vconfig on interface removal
Date: Mon, 17 Jan 2005 11:16:59 -0800 [thread overview]
Message-ID: <41EC0F2B.7010002@candelatech.com> (raw)
In-Reply-To: <41EA0A01.2020707@tomt.net>
Andre Tomt wrote:
> I sent this initially about a week ago, but nobody have said anything,
> not even a confirmation that its beeing looked into, or about me beeing
> silly - highly unusual on netdev! So I'm reposting (with slight
> modifications), boo, shame on me. Just a bit worried it slipped through
> the cracks.
My take on this is that it is a bug in the IPv6 code. If the IPv6 people
think that the VLAN code might could be causing this, then I am open to
suggestions as to how the VLAN code might be in error....
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2005-01-17 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 6:30 2.6.10 ipv6/8021q lockup on vconfig on interface removal Andre Tomt
2005-01-17 19:16 ` Ben Greear [this message]
2005-01-18 8:14 ` Hasso Tepper
2005-01-20 14:04 ` Andre Tomt
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=41EC0F2B.7010002@candelatech.com \
--to=greearb@candelatech.com \
--cc=andre@tomt.net \
--cc=netdev@oss.sgi.com \
/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).