netdev - Re: [PATCH net-next] xfrm: check function pointer of xfrm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 11 Nov 2013 10:52:22 -0800
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	baker.kernel@...il.com
Cc:	herbert@...dor.apana.org.au, davem@...emloft.net,
	steffen.klassert@...unet.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] xfrm: check function pointer of xfrm_mgr
 before use it

On Sun, 10 Nov 2013 22:25:56 +0800
baker.kernel@...il.com 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.

--
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