From: David Miller <davem@davemloft.net>
To: bootc@bootc.net
Cc: timo.teras@iki.fi, fan.du@windriver.com, sakiwit@gmail.com,
steffen.klassert@secunet.com, herbert@gondor.hengli.com.au,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: PANIC at net/xfrm/xfrm_output.c:125 (3.9.4)
Date: Wed, 26 Jun 2013 15:17:36 -0700 (PDT) [thread overview]
Message-ID: <20130626.151736.1797290996825764087.davem@davemloft.net> (raw)
In-Reply-To: <51C367DC.8050808@bootc.net>
From: Chris Boot <bootc@bootc.net>
Date: Thu, 20 Jun 2013 21:36:44 +0100
> On 06/06/2013 09:38, Timo Teras wrote:
>> On Thu, 06 Jun 2013 08:47:56 +0100
>> Chris Boot <bootc@bootc.net> wrote:
>>
>>> On 06/06/13 02:24, Fan Du wrote:
>>>> Hello Chris/Jean
>>>>
>>>> This issue might have already been fixed by this:
>>>> https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/net/xfrm/xfrm_output.c?id=497574c72c9922cf20c12aed15313c389f722fa0
>>>>
>>>>
>>>> Hope it helps.
>>>
>>> Hi Fan, Jean,
>>>
>>> Thanks, that looks like it's the patch for exactly my problem.
>>> Unfortunately I can't test it until next week now. :-/
>>>
>>> Timo/Dave: are there any plans to push this into 3.10-rc and/or
>>> stable? I seem to be able to hit the issue pretty reliably.
>>
>> It is already present in 3.10-rc3 [1], and Dave has it queued for
>> 3.9-stable [2].
>>
>> - Timo
>>
>> [1] http://lwn.net/Articles/551922/
>> [2] http://patchwork.ozlabs.org/patch/245594/
>
> I'm just wondering if this patch has got lost in the cracks; I reported
> the issue in 3.9.4 and 3.9.7 is just out without any sign of it. Have I
> missed something?
It got submitted to -stable last week.
next prev parent reply other threads:[~2013-06-26 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 21:47 PANIC at net/xfrm/xfrm_output.c:125 (3.9.4) Chris Boot
2013-06-06 1:04 ` Jean Sacren
2013-06-06 1:24 ` Fan Du
2013-06-06 7:47 ` Chris Boot
2013-06-06 8:38 ` Timo Teras
2013-06-06 8:57 ` Chris Boot
2013-06-20 20:36 ` Chris Boot
2013-06-26 22:17 ` David Miller [this message]
2013-06-27 22:07 ` Chris Boot
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=20130626.151736.1797290996825764087.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bootc@bootc.net \
--cc=fan.du@windriver.com \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sakiwit@gmail.com \
--cc=steffen.klassert@secunet.com \
--cc=timo.teras@iki.fi \
/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;
as well as URLs for NNTP newsgroup(s).