From: David Miller <davem@davemloft.net>
To: ast@kernel.org
Cc: daniel@iogearbox.net, netdev@vger.kernel.org,
bpf@vger.kernel.org, kernel-team@fb.com
Subject: Re: pull-request: bpf 2019-03-24
Date: Sun, 24 Mar 2019 23:45:57 -0400 (EDT) [thread overview]
Message-ID: <20190324.234557.645272669903498657.davem@davemloft.net> (raw)
In-Reply-To: <20190325025755.1757841-1-ast@kernel.org>
From: Alexei Starovoitov <ast@kernel.org>
Date: Sun, 24 Mar 2019 19:57:55 -0700
> The main changes are:
>
> 1) libbpf verision fix up from Daniel.
>
> 2) fix liveness propagation from Jakub.
>
> 3) fix verbose print of refcounted regs from Martin.
>
> 4) fix for large map allocations from Martynas.
>
> 5) fix use after free in sanitize_ptr_alu from Xu.
>
> Please consider pulling these changes from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
Pulled, thanks.
prev parent reply other threads:[~2019-03-25 3:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 2:57 pull-request: bpf 2019-03-24 Alexei Starovoitov
2019-03-25 3:45 ` 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=20190324.234557.645272669903498657.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@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).