All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Daniel Borkmann <daniel@iogearbox.net>, ast@fb.com
Cc: afabre@cloudflare.com, marek@cloudflare.com, bpf@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH bpf] bpf: fix sanitation rewrite in case of non-pointers
Date: Sat, 2 Mar 2019 13:11:57 +0300	[thread overview]
Message-ID: <96367b1a-4ab5-8f1d-1823-a65ba48fa3cc@cogentembedded.com> (raw)
In-Reply-To: <20190301210529.8218-1-daniel@iogearbox.net>

Hello!

On 02.03.2019 0:05, Daniel Borkmann wrote:

> Marek reported that he saw an issue with the below snippet in that
> timing measurements where off when loaded as unpriv while results

    Were?

> were reasonable when loaded as privileged:
> 
>      [...]
>      uint64_t a = bpf_ktime_get_ns();
>      uint64_t b = bpf_ktime_get_ns();
>      uint64_t delta = b - a;
>      if ((int64_t)delta > 0) {
>      [...]
> 
> Turns out there is a bug where a corner case is missing in the fix
> d3bd7413e0ca ("bpf: fix sanitation of alu op with pointer / scalar
> type from different paths"), namely fixup_bpf_calls() only checks
> whether aux has a non-zero alu_state, but it also needs to test for
> the case of BPF_ALU_NON_POINTER since in both occasions we need to
> skip the masking rewrite (as there is nothing to mask).
> 
> Fixes: d3bd7413e0ca ("bpf: fix sanitation of alu op with pointer / scalar type from different paths")
> Reported-by: Marek Majkowski <marek@cloudflare.com>
> Reported-by: Arthur Fabre <afabre@cloudflare.com>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> Link: https://lore.kernel.org/netdev/CAJPywTJqP34cK20iLM5YmUMz9KXQOdu1-+BZrGMAGgLuBWz7fg@mail.gmail.com/T/
[...]

MBR, Sergei

  parent reply	other threads:[~2019-03-02 10:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01 21:05 [PATCH bpf] bpf: fix sanitation rewrite in case of non-pointers Daniel Borkmann
2019-03-01 23:18 ` Song Liu
2019-03-01 23:22   ` Daniel Borkmann
2019-03-01 23:42     ` Song Liu
2019-03-02  5:30 ` Alexei Starovoitov
2019-03-02 10:11 ` Sergei Shtylyov [this message]
2019-03-05 14:12 ` Jakub Sitnicki
2019-03-05 14:30   ` Daniel Borkmann
2019-03-06  8:59     ` Jakub Sitnicki

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=96367b1a-4ab5-8f1d-1823-a65ba48fa3cc@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=afabre@cloudflare.com \
    --cc=ast@fb.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=marek@cloudflare.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 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.