From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <Alexander.Levin@microsoft.com>,
stable <stable@vger.kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
bpf@vger.kernel.org
Subject: Re: [stable] bpf: add bpf_jit_limit knob to restrict unpriv allocations
Date: Thu, 30 May 2019 20:48:55 +0100 [thread overview]
Message-ID: <1559245735.24330.6.camel@codethink.co.uk> (raw)
In-Reply-To: <20190530173100.GA23688@kroah.com>
On Thu, 2019-05-30 at 10:31 -0700, Greg Kroah-Hartman wrote:
> On Thu, May 30, 2019 at 06:18:00PM +0100, Ben Hutchings wrote:
> > On Mon, 2019-05-27 at 22:55 +0100, Ben Hutchings wrote:
> > > Please consider backporting this commit to 4.19-stable:
> > >
> > > commit ede95a63b5e84ddeea6b0c473b36ab8bfd8c6ce3
> > > Author: Daniel Borkmann <daniel@iogearbox.net>
> > > Date: Tue Oct 23 01:11:04 2018 +0200
> > >
> > > bpf: add bpf_jit_limit knob to restrict unpriv allocations
> > >
> > > No other stable branches are affected by the issue.
> >
> > Actually that's wrong; the commit introducing this was backported to
> > 4.4, 4.9, and 4.14. I haven't yet checked whether this fix applies
> > cleanly to them.
>
> It doesn't apply cleanly to those trees :(
OK, then I'll try backporting it at some point.
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
prev parent reply other threads:[~2019-05-30 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 21:55 [stable] bpf: add bpf_jit_limit knob to restrict unpriv allocations Ben Hutchings
2019-05-28 6:52 ` Greg Kroah-Hartman
2019-05-30 17:18 ` Ben Hutchings
2019-05-30 17:31 ` Greg Kroah-Hartman
2019-05-30 19:48 ` Ben Hutchings [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=1559245735.24330.6.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=Alexander.Levin@microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.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 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.