From: Stephen Hemminger <stephen@networkplumber•org>
To: Phil Sutter <phil@nwl•cc>
Cc: netdev@vger•kernel.org, Daniel Borkmann <daniel@iogearbox•net>
Subject: Re: [iproute PATCH] bpf: Make bytecode-file reading a little more robust
Date: Thu, 3 Aug 2017 15:59:42 -0700 [thread overview]
Message-ID: <20170803155942.4112575c@xeon-e3> (raw)
In-Reply-To: <20170802125756.26210-1-phil@nwl.cc>
On Wed, 2 Aug 2017 14:57:56 +0200
Phil Sutter <phil@nwl•cc> wrote:
> bpf_parse_string() will now correctly handle:
>
> - Extraneous whitespace,
> - OPs on multiple lines and
> - overlong file names.
>
> The added feature of allowing to have OPs on multiple lines (like e.g.
> tcpdump prints them) is rather a side effect of fixing detection of
> malformed bytecode files having random content on a second line, like
> e.g.:
>
> | 4,40 0 0 12,21 0 1 2048,6 0 0 262144,6 0 0 0
> | foobar
>
> Cc: Daniel Borkmann <daniel@iogearbox•net>
> Signed-off-by: Phil Sutter <phil@nwl•cc>
Looks good applied.
prev parent reply other threads:[~2017-08-03 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 12:57 [iproute PATCH] bpf: Make bytecode-file reading a little more robust Phil Sutter
2017-08-02 19:21 ` Daniel Borkmann
2017-08-03 22:59 ` Stephen Hemminger [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=20170803155942.4112575c@xeon-e3 \
--to=stephen@networkplumber$(echo .)org \
--cc=daniel@iogearbox$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=phil@nwl$(echo .)cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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