linux-kernel - Re: [2.6.34-rc5-git6] EIP: is at inet6_csk_bind

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <loom.20100425T162010-523@post.gmane.org>
Date:	Sun, 25 Apr 2010 14:26:12 +0000 (UTC)
From:	Jongman Heo <jongman.heo@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: [2.6.34-rc5-git6] EIP: is at inet6_csk_bind_conflict + 06xe/0xb7 	[ipv6]


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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/