selinux: add gfp argument to security_xfrm_policy_alloc and fix callers

security_xfrm_policy_alloc can be called in atomic context so the
allocation should be done with GFP_ATOMIC. Add an argument to let the
callers choose the appropriate way. In order to do so a gfp argument
needs to be added to the method xfrm_policy_alloc_security in struct
security_operations and to the internal function
selinux_xfrm_alloc_user. After that switch to GFP_ATOMIC in the atomic
callers and leave GFP_KERNEL as before for the rest.
The path that needed the gfp argument addition is:
security_xfrm_policy_alloc -> security_ops.xfrm_policy_alloc_security ->
all users of xfrm_policy_alloc_security (e.g. selinux_xfrm_policy_alloc) ->
selinux_xfrm_alloc_user (here the allocation used to be GFP_KERNEL only)

Now adding a gfp argument to selinux_xfrm_alloc_user requires us to also
add it to security_context_to_sid which is used inside and prior to this
patch did only GFP_KERNEL allocation. So add gfp argument to
security_context_to_sid and adjust all of its callers as well.

CC: Paul Moore <[email protected]>
CC: Dave Jones <[email protected]>
CC: Steffen Klassert <[email protected]>
CC: Fan Du <[email protected]>
CC: David S. Miller <[email protected]>
CC: LSM list <[email protected]>
CC: SELinux list <[email protected]>

Signed-off-by: Nikolay Aleksandrov <[email protected]>
Acked-by: Paul Moore <[email protected]>
Signed-off-by: Steffen Klassert <[email protected]>

0 files changed, 0 insertions, 0 deletions