linux-kernel - Re: 3.12-rc7 regression - network panic from ipv6

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: <20131029.174258.1677867676998240250.davem@davemloft.net>
Date:	Tue, 29 Oct 2013 17:42:58 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	mroos@...ux.ee
Cc:	hannes@...essinduktion.org, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org, steffen.klassert@...unet.com
Subject: Re: 3.12-rc7 regression - network panic from ipv6

From: Meelis Roos <mroos@...ux.ee>
Date: Tue, 29 Oct 2013 23:38:28 +0200 (EET)

>> > Some bad news - in a system where 3.12-rc6 and earlier worked fine, 
>> > 3.12-rc7 panics or hangs repeatedly with network traffic (torrent being 
>> > good test). First there is BUG from ipv6 code, followed by panic.
>> 
>> Could you do a bisect on this? There seems to be one commit for this
>> particular function _decode_session6:
>> 
>> commit bafd4bd4dcfa13145db7f951251eef3e10f8c278
>> Author: Steffen Klassert <steffen.klassert@...unet.com>
>> Date:   Mon Sep 9 10:38:38 2013 +0200
>> 
>>     xfrm: Decode sessions with output interface.
>>     
>>     The output interface matching does not work on forward
>>     policy lookups, the output interface of the flowi is
>>     always 0. Fix this by setting the output interface when
>>     we decode the session.
>> 
>> Maybe try to just revert this change locally and try again?
> 
> Yes, just reverting this patch on top of rc7 gets rid of the problem for 
> me.

Steffen please fix this or I'll have to revert.
--
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/