From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jan Hinnerk Stosch <janhinnerk.stosch@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: regression when connecting to ipv6 localhost
Date: Tue, 16 Oct 2012 18:55:22 +0200 [thread overview]
Message-ID: <1350406522.3954.1242.camel@edumazet-glaptop> (raw)
In-Reply-To: <1350405787.3954.1229.camel@edumazet-glaptop>
On Tue, 2012-10-16 at 18:43 +0200, Eric Dumazet wrote:
> On Tue, 2012-10-16 at 18:07 +0200, Jan Hinnerk Stosch wrote:
> > 2012/10/15 Jan Hinnerk Stosch <janhinnerk.stosch@gmail.com>:
> > >
> > > Yes. Attached..
> >
> > Today I read about the existence of the "git bisect" function and if I
> > have not done anything wrong the "bad commit" which lead to this
> > regression is ddbe503203855939946430e39bae58de11b70b69.
> > Perhaps this can help you.
>
> Interesting, I was about to ask you to do a bisection ;)
>
> So the hash value of ::1 was changed, and it has bad effect on your
> machine...
>
> Could it be hash collision and an old bug being uncovered ?
>
> Could you trace inet6_addr_hash() a bit ?
Dont bother, I found the bug. Its related to network namespaces
I'll send a fix asap.
Thanks !
next prev parent reply other threads:[~2012-10-16 16:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 15:38 regression when connecting to ipv6 localhost Jan Hinnerk Stosch
2012-10-14 19:29 ` Eric Dumazet
2012-10-14 19:48 ` Jan Hinnerk Stosch
2012-10-14 19:54 ` Eric Dumazet
2012-10-14 19:57 ` Jan Hinnerk Stosch
2012-10-14 20:25 ` Eric Dumazet
2012-10-14 20:26 ` Eric Dumazet
2012-10-14 20:28 ` Eric Dumazet
2012-10-14 20:39 ` Jan Hinnerk Stosch
2012-10-14 20:45 ` Eric Dumazet
2012-10-14 20:47 ` Eric Dumazet
2012-10-14 20:56 ` Jan Hinnerk Stosch
2012-10-14 21:02 ` Eric Dumazet
2012-10-14 21:07 ` Eric Dumazet
2012-10-14 21:21 ` Jan Hinnerk Stosch
2012-10-14 21:35 ` Eric Dumazet
2012-10-14 21:54 ` Jan Hinnerk Stosch
2012-10-14 22:01 ` Eric Dumazet
2012-10-14 22:11 ` Jan Hinnerk Stosch
2012-10-15 5:42 ` Eric Dumazet
2012-10-15 7:03 ` Jan Hinnerk Stosch
2012-10-15 7:14 ` Joe Perches
2012-10-15 7:39 ` Eric Dumazet
2012-10-15 7:43 ` Eric Dumazet
2012-10-15 11:25 ` Joe Perches
2012-10-15 12:31 ` Eric Dumazet
2012-10-15 13:10 ` Jan Hinnerk Stosch
2012-10-15 13:21 ` Eric Dumazet
2012-10-15 13:28 ` Jan Hinnerk Stosch
2012-10-16 16:07 ` Jan Hinnerk Stosch
2012-10-16 16:43 ` Eric Dumazet
2012-10-16 16:55 ` Eric Dumazet [this message]
2012-10-16 17:37 ` [PATCH] ipv6: addrconf: fix /proc/net/if_inet6 Eric Dumazet
2012-10-16 18:30 ` Jan Hinnerk Stosch
2012-10-16 18:39 ` David Miller
2012-10-16 22:01 ` Joe Perches
2012-10-16 18:55 ` David Miller
2012-10-15 9:25 ` regression when connecting to ipv6 localhost Eric Dumazet
2012-10-15 10:32 ` Jan Hinnerk Stosch
2012-10-15 9:07 ` Jan Ceuleers
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=1350406522.3954.1242.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=janhinnerk.stosch@gmail.com \
--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