netdev - Re: sctp_close/sk_free: kernel BUG at arch/x86/mm/physaddr.c:18!

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 05 Sep 2012 17:30:46 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Marc Kleine-Budde <mkl@...gutronix.de>
Cc:	Fengguang Wu <fengguang.wu@...el.com>,
	"H.K. Jerry Chu" <hkchu@...gle.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	networking <netdev@...r.kernel.org>, linux-can@...r.kernel.org
Subject: Re: sctp_close/sk_free: kernel BUG at arch/x86/mm/physaddr.c:18!

On Wed, 2012-09-05 at 17:01 +0200, Marc Kleine-Budde wrote:
> On 09/05/2012 04:55 PM, Fengguang Wu wrote:
> >>> This in turn means the problem doesn't come from the CAN patches, as
> >>> both trees have different CAN patches. I'm adding Eric W. Biederman on
> >>> Cc as he contributed some sctp patches between v3.6 and net-next/master.
> >>
> >> Anything is possible, but this seems unlikely as I don't think I touched
> >> anything close to that part of the code.
> > 
> > You are both right.  The bad commit turns out to be one of:
> > 
> > 1bed966cc3bd4042110129f0fc51aeeb59c5b200 Merge branch 'tcp_fastopen_server'
> > 168a8f58059a22feb9e9a2dcc1b8053dbbbc12ef tcp: TCP Fast Open Server - main code path
> > 8336886f786fdacbc19b719c1f7ea91eb70706d4 tcp: TCP Fast Open Server - support TFO listeners
> > 
> > Thanks,
> > Fengguang
> 
> Thanks for your work Fengguang.
> 
> Marc
> 

OK I have a good idea how to fix the bug, I will send a patch ASAP

Thanks


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html