From: Greg KH <gregkh@linuxfoundation.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: ast@kernel.org, jannh@google.com, stable@vger.kernel.org
Subject: Re: [PATCH stable/4.9 0/4] BPF stable patches for 4.9
Date: Fri, 22 Dec 2017 17:04:48 +0100 [thread overview]
Message-ID: <20171222160448.GA19498@kroah.com> (raw)
In-Reply-To: <20171222152905.3455-1-daniel@iogearbox.net>
On Fri, Dec 22, 2017 at 04:29:01PM +0100, Daniel Borkmann wrote:
> Hi Greg,
>
> please consider the following backported fixes for 4.9 inclusion.
>
> Thanks a lot!
All now applied, thanks!
greg k-h
prev parent reply other threads:[~2017-12-22 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 15:29 [PATCH stable/4.9 0/4] BPF stable patches for 4.9 Daniel Borkmann
2017-12-22 15:29 ` [PATCH stable/4.9 1/4] bpf: adjust insn_aux_data when patching insns Daniel Borkmann
2017-12-22 15:58 ` Patch "bpf: adjust insn_aux_data when patching insns" has been added to the 4.9-stable tree gregkh
2017-12-22 15:29 ` [PATCH stable/4.9 2/4] bpf: fix branch pruning logic Daniel Borkmann
2017-12-22 15:58 ` Patch "bpf: fix branch pruning logic" has been added to the 4.9-stable tree gregkh
2017-12-22 15:29 ` [PATCH stable/4.9 3/4] bpf: reject out-of-bounds stack pointer calculation Daniel Borkmann
2017-12-22 15:58 ` Patch "bpf: reject out-of-bounds stack pointer calculation" has been added to the 4.9-stable tree gregkh
2017-12-22 15:29 ` [PATCH stable/4.9 4/4] bpf: fix incorrect sign extension in check_alu_op() Daniel Borkmann
2017-12-22 15:58 ` Patch "bpf: fix incorrect sign extension in check_alu_op()" has been added to the 4.9-stable tree gregkh
2017-12-22 16:04 ` Greg KH [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=20171222160448.GA19498@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=jannh@google.com \
--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).