[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <51CCB7B6.10504@bootc.net>
Date: Thu, 27 Jun 2013 23:07:50 +0100
From: Chris Boot <bootc@...tc.net>
To: David Miller <davem@...emloft.net>
CC: timo.teras@....fi, fan.du@...driver.com, sakiwit@...il.com,
steffen.klassert@...unet.com, herbert@...dor.hengli.com.au,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: PANIC at net/xfrm/xfrm_output.c:125 (3.9.4)
On 26/06/2013 23:17, David Miller wrote:
> From: Chris Boot <bootc@...tc.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@...tc.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.
Dave,
Thank you, I see it's in 3.9.8 that has been just released.
Cheers,
Chris
--
Chris Boot
bootc@...tc.net
--
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
Powered by blists - more mailing lists