[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160727030117.GA23226@gondor.apana.org.au>
Date: Wed, 27 Jul 2016 11:01:18 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Vegard Nossum <vegard.nossum@...cle.com>
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 Wed, Jul 20, 2016 at 01:53:12PM +0200, Vegard Nossum wrote:
> On 07/20/2016 10:32 AM, Vegard Nossum wrote:
> >AFAICT this message is just printed whenever input validation fails.
> >This is a normal failure and we shouldn't be dumping the stack over it.
> >
> >Looks like it was originally a printk that was maybe incorrectly
> >upgraded to a WARN:
> >
> >commit 62db5cfd70b1ef53aa21f144a806fe3b78c84fab
> >Author: stephen hemminger <shemminger@...tta.com>
> >Date: Wed May 12 06:37:06 2010 +0000
> >
> > xfrm: add severity to printk
>
> Just FYI I'm also running into the
>
> // reset the timers here?
> WARN(1, "Don't know what to do with soft policy expire\n");
>
> in xfrm_add_pol_expire() from the same commit, but that looks
> potentially somewhat more serious (or at least it looks like we might
> want to do some sort of cleaning up), so I won't touch it for now.
It certainly shouldn't be a WARN, it probably shouldn't print
anything either.
Cheers,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Powered by blists - more mailing lists