Subject: Re: [PATCH net-next] xfrm: check function pointer of xfrm_mgr before use it

From: Stephen Hemminger <[email-masked]>
Date: Mon, 11 Nov 2013 10:52:22 -0800

On Sun, 10 Nov 2013 22:25:56 +0800
[email-masked] wrote:

> For current kernel source, there is no problem.
> 
> In our vpn product, we need a xfrm_km in kernel module
> to monitor the xfrm state change.
> thus, the 'acquire' and 'compile_policy' may be NULL.
> 
> So I think we should do the check before use it

The upstream kernel does not accept or make changes to accommodate code that
is not part of the kernel source.

The only way this change would be considered would be as part of a submission
of the kernel module. I.e. part 1 of N.

So if you are willing to submit your module upstream under GPLv2, then
it will be reviewed an possibly accepted. If you just want this change to
make your product easier, then sorry no.