All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: alexei.starovoitov@gmail.com, john.r.fastabend@gmail.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH net 0/3] Two BPF fixes for range marking
Date: Sun, 22 Oct 2017 01:13:46 +0100 (WEST)	[thread overview]
Message-ID: <20171022.011346.2270067847397243642.davem@davemloft.net> (raw)
In-Reply-To: <cover.1508545543.git.daniel@iogearbox.net>

From: Daniel Borkmann <daniel@iogearbox.net>
Date: Sat, 21 Oct 2017 02:34:20 +0200

> The set contains two fixes for direct packet access range
> markings and test cases for all direct packet access patterns
> that the verifier matches on.
> 
> They are targeted for net tree, note that once net gets merged
> into net-next, there will be a minor merge conflict due to
> signature change of the function find_good_pkt_pointers() as
> well as data_meta patterns present in net-next tree. You can
> just add bool false to the data_meta patterns and I will
> follow-up with properly converting the patterns for data_meta
> in a similar way.

Series applied and thanks for the merge info.

      parent reply	other threads:[~2017-10-22  0:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-21  0:34 [PATCH net 0/3] Two BPF fixes for range marking Daniel Borkmann
2017-10-21  0:34 ` [PATCH net 1/3] bpf: fix off by one for range markings with L{T,E} patterns Daniel Borkmann
2017-10-21 16:39   ` John Fastabend
2017-10-21  0:34 ` [PATCH net 2/3] bpf: fix pattern matches for direct packet access Daniel Borkmann
2017-10-21 16:39   ` John Fastabend
2017-10-21  0:34 ` [PATCH net 3/3] bpf: add test cases to bpf selftests to cover all access tests Daniel Borkmann
2017-10-21 16:40   ` John Fastabend
2017-10-22  0:13 ` 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=20171022.011346.2270067847397243642.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alexei.starovoitov@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=john.r.fastabend@gmail.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.