From: Steffen Klassert <steffen.klassert@secunet.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: net/xfrm: stack out-of-bounds in xfrm_flowi_sport
Date: Tue, 28 Feb 2017 14:43:21 +0100 [thread overview]
Message-ID: <20170228134321.GI694@gauss.secunet.com> (raw)
In-Reply-To: <CACT4Y+Y7xvGvAGVM_V2e+6+Tmmc-ZKdyUz3x-n6KvevW98iJnQ@mail.gmail.com>
Hi Dmitry.
On Tue, Feb 28, 2017 at 02:39:17PM +0100, Dmitry Vyukov wrote:
> On Wed, Feb 15, 2017 at 7:26 AM, Steffen Klassert
> <steffen.klassert@secunet.com> wrote:
> > On Tue, Feb 14, 2017 at 10:16:44AM +0100, Dmitry Vyukov wrote:
> >>
> >> I've run the repro with you patch and don't see the bug any more:
> >>
> >> Tested-by: Dmitry Vyukov <dvyukov@google.com>
> >
> > I've applied this to the ipsec tree now.
> >
> > Thanks for testing!
>
>
> Hi Steffen,
>
> Are you going to push this to Linus in this release? Still happens on
> upstream branch.
I'll do a pull request for the ipsec tree this week, should
go the way upstream then.
prev parent reply other threads:[~2017-02-28 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 14:46 net/xfrm: stack out-of-bounds in xfrm_flowi_sport Dmitry Vyukov
2017-02-14 7:08 ` Steffen Klassert
2017-02-14 8:41 ` Dmitry Vyukov
2017-02-14 9:08 ` Steffen Klassert
2017-02-14 9:16 ` Dmitry Vyukov
2017-02-15 6:26 ` Steffen Klassert
2017-02-28 13:39 ` Dmitry Vyukov
2017-02-28 13:43 ` Steffen Klassert [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=20170228134321.GI694@gauss.secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller@googlegroups.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