xfrm: Report user triggered expirations against the users socket
authorEric W. Biederman <ebiederm@xmission.com>
Fri, 7 Sep 2012 21:17:17 +0000 (21:17 +0000)
committerDavid S. Miller <davem@davemloft.net>
Mon, 10 Sep 2012 19:34:30 +0000 (15:34 -0400)
commitc6bb8136c95ce16545f8c4028e958c0ee6c86f23
tree0ec3bd7a23eccd33e3f1857de1637715eb65c17d
parent15e473046cb6e5d18a4d0057e61d76315230382b
xfrm: Report user triggered expirations against the users socket

When a policy expiration is triggered from user space the request
travels through km_policy_expired and ultimately into
xfrm_exp_policy_notify which calls build_polexpire.  build_polexpire
uses the netlink port passed to km_policy_expired as the source port for
the netlink message it builds.

When a state expiration is triggered from user space the request travles
through km_state_expired and ultimately into xfrm_exp_state_notify which
calls build_expire.  build_expire uses the netlink port passed to
km_state_expired as the source port for the netlink message it builds.

Pass nlh->nlmsg_pid from the user generated netlink message that
requested the expiration to km_policy_expired and km_state_expired
instead of current->pid which is not a netlink port number.

Cc: Jamal Hadi Salim <hadi@cyberus.ca>
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Acked-by: Jamal Hadi Salim <jhs@mojatatu.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/xfrm/xfrm_user.c