All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Fan Du <fan.du@windriver.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/3] xfrm: check user specified spi for IPComp
Date: Fri, 6 Dec 2013 12:44:27 +0100	[thread overview]
Message-ID: <20131206114427.GH31491@secunet.com> (raw)
In-Reply-To: <1385607161-27597-2-git-send-email-fan.du@windriver.com>

On Thu, Nov 28, 2013 at 10:52:39AM +0800, Fan Du wrote:
> 
> diff --git a/net/xfrm/xfrm_user.c b/net/xfrm/xfrm_user.c
> index f964d4c..52efe71 100644
> --- a/net/xfrm/xfrm_user.c
> +++ b/net/xfrm/xfrm_user.c
> @@ -209,7 +209,8 @@ static int verify_newsa_info(struct xfrm_usersa_info *p,
>  		    attrs[XFRMA_ALG_AUTH]	||
>  		    attrs[XFRMA_ALG_AUTH_TRUNC]	||
>  		    attrs[XFRMA_ALG_CRYPT]	||
> -		    attrs[XFRMA_TFCPAD])
> +		    attrs[XFRMA_TFCPAD] ||
> +			(ntohl(p->id.spi) >= 0x10000))

Please align the above line to the rest of this block.

  reply	other threads:[~2013-12-06 11:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28  2:52 [PATCH net-next 0/3] IPComp fixes Fan Du
2013-11-28  2:52 ` [PATCH net-next 1/3] xfrm: check user specified spi for IPComp Fan Du
2013-12-06 11:44   ` Steffen Klassert [this message]
2013-11-28  2:52 ` [PATCH net-next 2/3] xfrm: clamp down spi range for IPComp when allocating spi Fan Du
2013-12-06 11:42   ` Steffen Klassert
2013-12-09  6:27     ` Fan Du
2013-12-09  8:57       ` Steffen Klassert
2013-12-09  9:13         ` Fan Du
2013-12-09  9:51           ` Steffen Klassert
2013-12-09  9:58             ` Fan Du
2013-11-28  2:52 ` [PATCH net-next 3/3] xfrm: Restrict "level use" for IPComp configuration Fan Du
2013-12-09 10:38   ` Steffen Klassert
2013-12-10  2:39     ` Fan Du
2013-12-10 13:11       ` Steffen Klassert
2013-12-13  9:16         ` Fan Du
2013-12-06  9:58 ` [PATCH net-next 0/3] IPComp fixes Fan Du

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=20131206114427.GH31491@secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=davem@davemloft.net \
    --cc=fan.du@windriver.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.