All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: Generic eBPF hardening
Date: Thu, 17 May 2018 16:39:07 -0700	[thread overview]
Message-ID: <20180517233907.GD4486@tassilo.jf.intel.com> (raw)
In-Reply-To: <20180517232115.mwmns6w6t32mjeze@ast-mbp>

> I disagree with 'cheap' assessment.
> The main use case for unprivileged bpf is so_reuseport and socket filters.
> It's critical path of networking receive side.
> Adding lfence after every program won't be cheap.

I don't think we need any lfence at all. It makes no difference for 
stack reuse. 

All we need is stack clear for the locations that are script controlled.
That should be quite cheap.

Register clearing would be nice, and should be also cheap.

-Andi

  reply	other threads:[~2018-05-17 23:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 20:55 [MODERATED] Generic eBPF hardening Dave Hansen
2018-05-17 22:22 ` [MODERATED] " Alexei Starovoitov
2018-05-17 22:54   ` Andi Kleen
2018-05-17 23:21     ` Alexei Starovoitov
2018-05-17 23:39       ` Andi Kleen [this message]
2018-05-18 18:18       ` Dave Hansen
2018-05-18 22:26         ` Alexei Starovoitov
2018-05-17 23:13   ` Dave Hansen
2018-05-17 23:24     ` Alexei Starovoitov

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=20180517233907.GD4486@tassilo.jf.intel.com \
    --to=ak@linux.intel.com \
    --cc=speck@linutronix.de \
    /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.