From: David Miller <davem@davemloft.net>
To: steffen.klassert@secunet.com
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: pull request (net): ipsec 2018-05-31
Date: Fri, 01 Jun 2018 13:26:24 -0400 (EDT) [thread overview]
Message-ID: <20180601.132624.1112113043537294329.davem@davemloft.net> (raw)
In-Reply-To: <20180531102326.5728-1-steffen.klassert@secunet.com>
From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Thu, 31 May 2018 12:23:24 +0200
> 1) Avoid possible overflow of the offset variable
> in _decode_session6(), this fixes an infinite
> lookp there. From Eric Dumazet.
>
> 2) We may use an error pointer in the error path of
> xfrm_bundle_create(). Fix this by returning this
> pointer directly to the caller.
>
> Please pull or let me know if there are problems.
Pulled, thanks Steffen.
prev parent reply other threads:[~2018-06-01 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 10:23 pull request (net): ipsec 2018-05-31 Steffen Klassert
2018-05-31 10:23 ` [PATCH 1/2] xfrm6: avoid potential infinite loop in _decode_session6() Steffen Klassert
2018-05-31 10:23 ` [PATCH 2/2] xfrm Fix potential error pointer dereference in xfrm_bundle_create Steffen Klassert
2018-06-01 17:26 ` David Miller [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=20180601.132624.1112113043537294329.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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).