Messages in this thread | | | Date | Sun, 25 Apr 2010 18:31:31 +0200 | Subject | Re: [2.6.34-rc5-git6] EIP: is at inet6_csk_bind_conflict + 06xe/0xb7 [ipv6] | From | Sedat Dilek <> |
| |
[ CCing netdev ML ]
Confirmed: The revert-patch [1] fixes the problem here.
See also "Bug 15847 - crash in inet6_csk_bind_conflict" [2].
Feel free to add a... Tested-by: Sedat Dilek <sedat.dilek@gmail.com>
- Sedat -
[1] https://patchwork.kernel.org/patch/94959/ [2] https://bugzilla.kernel.org/show_bug.cgi?id=15847
2010/4/25 Piotr Hosowicz <piotr@hosowicz.com>: > On 25.04.2010 17:11, Sedat Dilek wrote: >> >> [ Please CC - I am not subscribed to LKML ] >> >> [QUOTE] >> >> On 25.04.2010 16:26, Jongman Heo wrote: >> >>> I also hit this bug today. >> >> I also hit similar bug, maybe it is the same. >> >>> Doing git bisect, first bad commit was >>> >>> commit fda48a0d7a8412cedacda46a9c0bf8ef9cd13559 >>> tcp: bind() fix when many ports are bound >>> >>> Reverting above commit fixes the problem. >> >> How to do it? Would you please publish a reverting patch? >> >> Regards, >> >> Piotr Hosowicz >> >> [/QUOTE] >> >> Hi, >> >> did forget to mention 2.6.34-rc5-git5 was OK. >> >> Revering this commit did not help: >> >> commit f4f914b58019f0e50d521bbbadfaee260d766f95 >> net: ipv6 bind to device issue >> >> After looking into net-2.6 GIT repository, "tcp: bind() fix when many >> ports are bound" could cause indeed the problems here, too. >> Building now.... >> >> Regards, >> - Sedat - >> >> P.S.: Attached 0001-Revert-tcp-bind-fix-when-many-ports-are-bound.patch > > Thanks a lot. Applied and building now. > > Regards, > > Piotr Hosowicz > > -- > Z cyklu "Uroki demokracji", czyli pytania i odpowiedzi w teledurniejach: > - W którym kraju znajduje się Mount Everest? > - Hm, to nie Szkocja, prawda? > NP: Mark Knopfler - Cleaning My Gun > NB: 2.6.34-rc5-git5 > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |