From: Greg KH <gregkh@linuxfoundation.org>
To: Rafael David Tinoco <rafaeldtinoco@gmail.com>
Cc: stable@vger.kernel.org, andriin@fb.com, daniel@iogearbox.net,
yanivagman@gmail.com
Subject: Re: [PATCH] bpf: Track contents of read-only maps as scalars
Date: Wed, 1 Sep 2021 10:41:28 +0200 [thread overview]
Message-ID: <YS88uFRrXFW4DOen@kroah.com> (raw)
In-Reply-To: <20210821203108.215937-2-rafaeldtinoco@gmail.com>
On Sat, Aug 21, 2021 at 05:31:08PM -0300, Rafael David Tinoco wrote:
> commit a23740ec43ba022dbfd139d0fe3eff193216272b upstream.
>
> Maps that are read-only both from BPF program side and user space side
> have their contents constant, so verifier can track referenced values
> precisely and use that knowledge for dead code elimination, branch
> pruning, etc. This patch teaches BPF verifier how to do this.
>
> [Backport]
> Already includes further build fix made at commit 2dedd7d21655 ("bpf:
> Fix cast to pointer from integer of different size warning").
Do not do that, let us queue up the original commits instead please.
thanks,
greg k-h
prev parent reply other threads:[~2021-09-01 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-21 20:31 [PATCH] bpf: Track contents of read-only maps as scalars Rafael David Tinoco
2021-08-21 20:31 ` Rafael David Tinoco
2021-09-01 8:41 ` 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=YS88uFRrXFW4DOen@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriin@fb.com \
--cc=daniel@iogearbox.net \
--cc=rafaeldtinoco@gmail.com \
--cc=stable@vger.kernel.org \
--cc=yanivagman@gmail.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;
as well as URLs for NNTP newsgroup(s).