From: Jongman Heo <jongman.heo@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6.34-rc5-git6] EIP: is at inet6_csk_bind_conflict + 06xe/0xb7 [ipv6]
Date: Sun, 25 Apr 2010 14:26:12 +0000 (UTC) [thread overview]
Message-ID: <loom.20100425T162010-523@post.gmane.org> (raw)
In-Reply-To: m2z2d0a357f1004250613of5215185z1490aaae7363b161@mail.gmail.com
Sedat Dilek <sedat.dilek <at> googlemail.com> writes:
>
> Hi,
>
> I have built today 2.6.34-rc5-git6 Linux-kernel on a 32-bit Debian/sid
system.
>
> Unfortunately, my machine hangs while startup at sshd-start (from
> memory + written down):
>
> [...]
> EIP: is at inet6_csk_bind_conflict + 06xe/0xb7 [ipv6]
> Pid: 2150, comm: sshd Not tainted $(uname -r) #1 30AC/HP Compaq nc6400
> (RH72EA#ABD)
> [...]
>
> I suspect one of the latest IPv6 commits as culprit, especially:
>
> commit f4f914b58019f0e50d521bbbadfaee260d766f95
> net: ipv6 bind to device issue
>
> ...or...
> commit f2228f785a9d97307aa8ba709088cfda6c3df73f
> ipv6: allow to send packet after receiving ICMPv6 Too Big message with
> MTU field less than IPV6_MIN_MTU
>
> Could not test yet by reverting.
>
> Kind Regards,
> - Sedat -
>
I also hit this bug today.
Doing git bisect, first bad commit was
commit fda48a0d7a8412cedacda46a9c0bf8ef9cd13559
tcp: bind() fix when many ports are bound
Reverting above commit fixes the problem.
Regards.
next prev parent reply other threads:[~2010-04-25 14:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 13:13 [2.6.34-rc5-git6] EIP: is at inet6_csk_bind_conflict + 06xe/0xb7 [ipv6] Sedat Dilek
2010-04-25 14:26 ` Jongman Heo [this message]
2010-04-25 14:46 ` Piotr Hosowicz
-- strict thread matches above, loose matches on Subject: below --
2010-04-25 15:11 Sedat Dilek
2010-04-25 15:23 ` Piotr Hosowicz
2010-04-25 16:31 ` Sedat Dilek
2010-04-25 16:36 ` Piotr Hosowicz
2010-04-25 16:39 ` Eric Dumazet
2010-04-25 16:55 ` Sedat Dilek
2010-04-25 17:01 ` Piotr Hosowicz
2010-04-25 17:08 ` Eric Dumazet
2010-04-25 17:25 ` Sedat Dilek
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=loom.20100425T162010-523@post.gmane.org \
--to=jongman.heo@gmail.com \
--cc=linux-kernel@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