Skip to contentSkip to conversation

lsm: export the security_skb_owned_by() function

PATCH In review Paul Moore 2 participants 3 messages Apr 12, 2013

Subsystems (3)
lore
Share & tools
lore

Paul Moore

author
#0 lore raw

PATCH 1/1 lsm: export the security_skb_owned_by() function

Another bit we missed when adding the skb_owned_by() hook.

---
 security/security.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
security/security.c +1 -1
index 03f248b..9eebd6b 100644
@@ -1294,7 +1294,7 @@ void security_skb_owned_by(struct sk_buff *skb, struct sock *sk)
 {
 	security_ops->skb_owned_by(skb, sk);
 }
-
+EXPORT_SYMBOL(security_skb_owned_by);
 #endif	/* CONFIG_SECURITY_NETWORK */
 
 #ifdef CONFIG_SECURITY_NETWORK_XFRM
maintainer
#1 lore raw

From: Paul Moore <[email protected]>
Date: Fri, 12 Apr 2013 11:43:00 -0400

Quoted 3 lines

Another bit we missed when adding the skb_owned_by() hook.

CONFIG_SECURITY is a bool, as is ipv4, so neither the definition nor the call sites can be modular.

Therefore no export is needed.

author
#2 lore raw
Quoted 11 lines · David Miller

From: Paul Moore <[email protected]>
Date: Fri, 12 Apr 2013 11:43:00 -0400

Quoted 3 lines

Another bit we missed when adding the skb_owned_by() hook.

CONFIG_SECURITY is a bool, as is ipv4, so neither the definition nor the call sites can be modular.

Therefore no export is needed.

Yep, sorry about that.

Signature · 2 lines
paul moore
security and virtualization @ redhat