From: Julian Anastasov <ja@ssi.bg>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: Meelis Roos <mroos@linux.ee>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, steffen.klassert@secunet.com
Subject: Re: 3.12-rc7 regression - network panic from ipv6
Date: Tue, 29 Oct 2013 23:21:24 +0200 (EET) [thread overview]
Message-ID: <alpine.LFD.2.03.1310292310180.2045@ssi.bg> (raw)
In-Reply-To: <20131029210758.GA18323@order.stressinduktion.org>
Hello,
On Tue, 29 Oct 2013, Hannes Frederic Sowa wrote:
> On Tue, Oct 29, 2013 at 10:33:36PM +0200, Meelis Roos wrote:
> > 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@secunet.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?
At first look this change can work only for
forwarding, for output the skb_dst is attached later
in icmpv6_push_pending_frames. May be a check for present
skb_dst is needed.
Regards
--
Julian Anastasov <ja@ssi.bg>
next prev parent reply other threads:[~2013-10-29 21:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 20:33 Meelis Roos
2013-10-29 21:07 ` Hannes Frederic Sowa
2013-10-29 21:21 ` Julian Anastasov [this message]
2013-10-29 21:38 ` Meelis Roos
2013-10-29 21:42 ` David Miller
2013-10-30 13:09 ` Steffen Klassert
2013-10-30 21:41 ` mroos
2013-10-31 4:35 ` David Miller
2013-11-01 7:56 ` Steffen Klassert
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=alpine.LFD.2.03.1310292310180.2045@ssi.bg \
--to=ja@ssi.bg \
--cc=hannes@stressinduktion.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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
Powered by JetHome