[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZFOIsffqSV07WzRt@gondor.apana.org.au>
Date: Thu, 4 May 2023 18:28:01 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: syzbot <syzbot+b3346cca0c23c839e787@...kaller.appspotmail.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
pabeni@...hat.com, steffen.klassert@...unet.com,
syzkaller-bugs@...glegroups.com,
Alexey Dobriyan <adobriyan@...il.com>,
Eric Biederman <ebiederm@...ssion.com>
Subject: Re: [syzbot] [net?] WARNING in xfrm_policy_fini (2)
On Tue, Apr 11, 2023 at 05:22:53PM -0700, syzbot wrote:
>
> WARNING: CPU: 0 PID: 41 at net/xfrm/xfrm_policy.c:4176 xfrm_policy_fini+0x2f2/0x3c0 net/xfrm/xfrm_policy.c:4176
This code was broken from day one. Prior to netns this policy
fini function didn't exist.
With netns, somehow it wants to get rid of all xfrm policies.
However, it's not doing a very good job at it because it only
deletes the global policies, and not the socket policies.
Therefore this is completely expected to fail.
Do we have a netns maintainer? What is this supposed to do?
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