From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Anirudh Gupta <anirudhrudr@gmail.com>,
Anirudh Gupta <anirudh.gupta@sophos.com>,
"David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] xfrm: Fix xfrm sel prefix length validation
Date: Tue, 28 May 2019 09:44:10 +0200 [thread overview]
Message-ID: <20190528074410.GD14601@gauss3.secunet.de> (raw)
In-Reply-To: <20190522031700.ynp6ctodqlztybb2@gondor.apana.org.au>
On Wed, May 22, 2019 at 11:17:00AM +0800, Herbert Xu wrote:
> On Tue, May 21, 2019 at 08:59:47PM +0530, Anirudh Gupta wrote:
> > Family of src/dst can be different from family of selector src/dst.
> > Use xfrm selector family to validate address prefix length,
> > while verifying new sa from userspace.
> >
> > Validated patch with this command:
> > ip xfrm state add src 1.1.6.1 dst 1.1.6.2 proto esp spi 4260196 \
> > reqid 20004 mode tunnel aead "rfc4106(gcm(aes))" \
> > 0x1111016400000000000000000000000044440001 128 \
> > sel src 1011:1:4::2/128 sel dst 1021:1:4::2/128 dev Port5
> >
> > Fixes: 07bf7908950a ("xfrm: Validate address prefix lengths in the xfrm selector.")
> > Signed-off-by: Anirudh Gupta <anirudh.gupta@sophos.com>
>
> Acked-by: Herbert Xu <herbert@gondor.apana.org.au>
Patch applied, thanks everyone!
next prev parent reply other threads:[~2019-05-28 7:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 15:29 Anirudh Gupta
2019-05-22 3:17 ` Herbert Xu
2019-05-28 7:44 ` Steffen Klassert [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-21 8:22 Anirudh Gupta
2019-05-21 12:22 ` Herbert Xu
2019-05-20 9:31 Anirudh Gupta
2019-05-20 15:32 ` Herbert Xu
2019-05-20 17:05 ` Anirudh Gupta
[not found] ` <CAN2cbVe3WNj8cR1dLysCP46-LwiHZYMWRpowA+bzNpyZRexSaA@mail.gmail.com>
2019-05-21 2:49 ` Herbert Xu
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=20190528074410.GD14601@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=anirudh.gupta@sophos.com \
--cc=anirudhrudr@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®