[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5798583F.6060404@oracle.com>
Date: Wed, 27 Jul 2016 08:44:15 +0200
From: Vegard Nossum <vegard.nossum@...cle.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Stephen Hemminger <stephen@...workplumber.org>,
netdev@...r.kernel.org,
Steffen Klassert <steffen.klassert@...unet.com>
Subject: Re: [PATCH] xfrm: use printk instead of WARN for bad policy reporting
On 07/27/2016 08:31 AM, Herbert Xu wrote:
> On Wed, Jul 27, 2016 at 08:20:57AM +0200, Vegard Nossum wrote:
>>
>> Here's another patch to remove that too.
>>
>> I don't actually *use* this code myself and I feel the justification
>> I've given for removing the WARN to be a bit weak, so if you don't take
>> the patch I'll just keep it in my local tree to keep it from showing up
>> again during fuzzing.
>
> Please just kill the whole else clause. For soft policy expires
> we simply need to relay a message to the KM and nothing more.
Try #2 :-)
Vegard
View attachment "0001-xfrm-get-rid-of-another-incorrect-WARN.patch" of type "text/x-patch" (1156 bytes)
Powered by blists - more mailing lists