netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: alexei.starovoitov@gmail.com, ast@fb.com, netdev@vger.kernel.org
Subject: Re: bpf pointer alignment validation
Date: Wed, 10 May 2017 11:57:20 -0400 (EDT)	[thread overview]
Message-ID: <20170510.115720.1396306489898364855.davem@davemloft.net> (raw)
In-Reply-To: <59133716.7060800@iogearbox.net>

From: Daniel Borkmann <daniel@iogearbox.net>
Date: Wed, 10 May 2017 17:51:50 +0200

> Would probably be good nevertheless to have this as a flag for
> program loads, which gets then passed through to the verifier to
> explicitly enable strict alignment checks.
> 
> Might certainly aide developing & testing programs on archs with
> efficient unaligned access and later actually running them on archs
> that don't have it. (And at minimum, it also helps for checking
> the test suite against the verifier.)

Ok, I can implement this flag.

The only question is where to put it?  An unused bit in the program
type? :-)

  reply	other threads:[~2017-05-10 15:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 20:20 bpf pointer alignment validation David Miller
2017-05-06  2:47 ` David Miller
2017-05-08 10:49   ` Daniel Borkmann
2017-05-08 15:04     ` David Miller
2017-05-09 18:32     ` David Miller
2017-05-10  5:57       ` Alexei Starovoitov
2017-05-10 11:12         ` David Laight
2017-05-10 15:33         ` David Miller
2017-05-10 15:51           ` Daniel Borkmann
2017-05-10 15:57             ` David Miller [this message]
2017-05-10 16:15               ` Alexei Starovoitov
2017-05-10 16:21               ` Daniel Borkmann
2017-05-10 16:45                 ` David Miller
2017-05-08 17:30   ` 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=20170510.115720.1396306489898364855.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alexei.starovoitov@gmail.com \
    --cc=ast@fb.com \
    --cc=daniel@iogearbox.net \
    --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).