Netdev List
 help / color / mirror / Atom feed
From: Martin Willi <martin@strongswan.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] xfrm: Notify changes in UDP encapsulation via netlink
Date: Tue, 28 Oct 2008 21:44:20 +0100	[thread overview]
Message-ID: <1225226660.6976.18.camel@martin> (raw)
In-Reply-To: <20081028.114828.158507859.davem@davemloft.net>

> I don't see the code which will actually invoke the new
> ->new_mapping() method (either here or in a follow-on patch), so it's
> impossible to review these changes.

The patch is complete, sorry for being unclear.

xfrm_send_mapping is an implementation of a xfrm_mgr operation. 

>  static struct xfrm_mgr netlink_mgr = {
>         .id             = "netlink",
>         .notify         = xfrm_send_state_notify,
>         .notify_policy  = xfrm_send_policy_notify,
>         .report         = xfrm_send_report,
>         .migrate        = xfrm_send_migrate,
> +       .new_mapping    = xfrm_send_mapping,
> };

This operation is invoked from net/ipv4/esp4.c through the
km_new_mapping() function, km_new_mapping() invokes all registered key
managers. It is already implemented in the PF_KEY interface (pfkeyv2_mgr
in af_key.c), but is missing in the netlink xfrm interface. The patch
adds this functionality to the netlink interface.



  reply	other threads:[~2008-10-28 21:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28  8:51 [PATCH] xfrm: Notify changes in UDP encapsulation via netlink Martin Willi
2008-10-28 18:48 ` David Miller
2008-10-28 20:44   ` Martin Willi [this message]
2008-10-28 22:34     ` David Miller
2008-10-28 23:01 ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2008-10-13  9:27 Martin Willi
2008-10-13 10:03 ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1225226660.6976.18.camel@martin \
    --to=martin@strongswan.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox