From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Steffen Klassert <steffen.klassert@secunet.com>,
<netdev@vger.kernel.org>
Subject: pull request (net-next): ipsec-next 2016-09-23
Date: Fri, 23 Sep 2016 09:14:40 +0200 [thread overview]
Message-ID: <1474614882-25253-1-git-send-email-steffen.klassert@secunet.com> (raw)
Only two patches this time:
1) Fix a comment reference to struct xfrm_replay_state_esn.
From Richard Guy Briggs.
2) Convert xfrm_state_lookup to rcu, we don't need the
xfrm_state_lock anymore in the input path.
From Florian Westphal.
Please pull or let me know if there are problems.
Thanks!
The following changes since commit 2d2be8cab26ed918e94d2deae89580003242a123:
bpf: fix range propagation on direct packet access (2016-09-08 17:28:37 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git master
for you to fetch changes up to c2f672fc94642bae96821a393f342edcfa9794a6:
xfrm: state lookup can be lockless (2016-09-21 12:37:29 +0200)
----------------------------------------------------------------
Florian Westphal (1):
xfrm: state lookup can be lockless
Richard Guy Briggs (1):
xfrm: fix header file comment reference to struct xfrm_replay_state_esn
include/uapi/linux/xfrm.h | 2 +-
net/xfrm/xfrm_state.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
next reply other threads:[~2016-09-23 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 7:14 Steffen Klassert [this message]
2016-09-23 7:14 ` [PATCH 1/2] xfrm: fix header file comment reference to struct xfrm_replay_state_esn Steffen Klassert
2016-09-23 7:14 ` [PATCH 2/2] xfrm: state lookup can be lockless Steffen Klassert
2016-09-24 12:19 ` pull request (net-next): ipsec-next 2016-09-23 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=1474614882-25253-1-git-send-email-steffen.klassert@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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