From: Steffen Klassert <steffen.klassert@secunet.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <stable@vger.kernel.org>, David Miller <davem@davemloft.net>
Subject: Re: [PATCH -stable] ipsec: Fix aborted xfrm policy dump crash
Date: Mon, 30 Oct 2017 11:09:08 +0100 [thread overview]
Message-ID: <20171030100908.GC30509@secunet.com> (raw)
In-Reply-To: <20171030095359.GB12685@kroah.com>
On Mon, Oct 30, 2017 at 10:53:59AM +0100, Greg KH wrote:
> On Mon, Oct 30, 2017 at 10:45:10AM +0100, Greg KH wrote:
> > On Tue, Oct 24, 2017 at 02:14:47PM +0200, Steffen Klassert wrote:
> > > On Tue, Oct 24, 2017 at 02:12:03PM +0200, Greg KH wrote:
> > > > On Tue, Oct 24, 2017 at 02:01:35PM +0200, Steffen Klassert wrote:
> > > > > Please queue up the following patch for -stable.
> > > > > It fixes a security bug and should be applied to
> > > > > all maintained stable versions.
> > > > >
> > > > > From: Herbert Xu <herbert@gondor.apana.org.au>
> > > > > Date: Thu, 19 Oct 2017 20:51:10 +0800
> > > > > Subject: [PATCH] ipsec: Fix aborted xfrm policy dump crash
> > > > >
> > > > > [ Upstream commit 1137b5e2529a8f5ca8ee709288ecba3e68044df2 ]
> > > >
> > > > That commit id is not in Linus's tree, where did you get it from?
> > >
> > > It is in the 'net' tree from David Miller. It was merged to 'net'
> > > today from the ipsec tree.
> >
> > Ok, it's now in Linus's tree, so now queued up, thanks!
>
> But it fails in 4.4 due to api changes. If you think it is needed
> there, and you are able to, could you provide a backported patch?
I'll have a look at it, thanks for the info!
next prev parent reply other threads:[~2017-10-30 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 12:01 [PATCH -stable] ipsec: Fix aborted xfrm policy dump crash Steffen Klassert
2017-10-24 12:12 ` Greg KH
2017-10-24 12:14 ` Steffen Klassert
2017-10-30 9:45 ` Greg KH
2017-10-30 9:53 ` Greg KH
2017-10-30 10:09 ` Steffen Klassert [this message]
2017-10-24 12:16 ` David Miller
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=20171030100908.GC30509@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).