From: Fan Du <fan.du@windriver.com>
To: <steffen.klassert@secunet.com>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: [PATCHv4 net-next 6/6] xfrm: Don't prohibit AH from using ESN feature
Date: Wed, 15 Jan 2014 15:13:15 +0800 [thread overview]
Message-ID: <1389769995-350-7-git-send-email-fan.du@windriver.com> (raw)
In-Reply-To: <1389769995-350-1-git-send-email-fan.du@windriver.com>
Clear checking when user try to use ESN through netlink keymgr for AH.
As only ESP and AH support ESN feature according to RFC.
Signed-off-by: Fan Du <fan.du@windriver.com>
---
net/xfrm/xfrm_user.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net/xfrm/xfrm_user.c b/net/xfrm/xfrm_user.c
index 3348566..9a80aa9 100644
--- a/net/xfrm/xfrm_user.c
+++ b/net/xfrm/xfrm_user.c
@@ -142,7 +142,8 @@ static inline int verify_replay(struct xfrm_usersa_info *p,
if (!rt)
return 0;
- if (p->id.proto != IPPROTO_ESP)
+ /* As only ESP and AH support ESN feature. */
+ if ((p->id.proto != IPPROTO_ESP) && (p->id.proto != IPPROTO_AH))
return -EINVAL;
if (p->replay_window != 0)
--
1.7.9.5
prev parent reply other threads:[~2014-01-15 7:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 7:13 [PATCHv4 net-next 0/6] xfrm: Add ESN support for AH Fan Du
2014-01-15 7:13 ` [PATCHv4 net-next 1/6] skbuff: Introduce skb_to_sgvec_nomark to map skb without mark new end Fan Du
2014-01-15 7:13 ` [PATCHv4 net-next 2/6] {IPv4,xfrm} Add ESN support for AH egress part Fan Du
2014-01-15 7:13 ` [PATCHv4 net-next 3/6] {IPv4,xfrm} Add ESN support for AH ingress part Fan Du
2014-01-16 9:56 ` Steffen Klassert
2014-01-15 7:13 ` [PATCHv4 net-next 4/6] {IPv6,xfrm} Add ESN support for AH egress part Fan Du
2014-01-15 7:13 ` [PATCHv4 net-next 5/6] {IPv6,xfrm} Add ESN support for AH ingress part Fan Du
2014-01-15 7:13 ` Fan Du [this message]
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=1389769995-350-7-git-send-email-fan.du@windriver.com \
--to=fan.du@windriver.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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;
as well as URLs for NNTP newsgroup(s).