Subject: Re: [PATCH] xfrm: Report user triggered expirations against the users socket

From: Jamal Hadi Salim <[email-masked]>
Date: Sat, 08 Sep 2012 07:48:14 -0400

On 12-09-08 03:17 AM, Eric W. Biederman wrote:
> When a policy expiration is triggered from user space the request
> travles 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 <[email-masked]>
> Signed-off-by: "Eric W. Biederman" <[email-masked]>
>

I suppose.
Acked-by: Jamal Hadi Salim <[email-masked]>

cheers,
jamal