From: Stephen Hemminger <stephen@networkplumber.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: jhs@mojatatu.com, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] tc: m_bpf: fix next arg selection after tc opcode
Date: Tue, 24 Mar 2015 15:46:23 -0700 [thread overview]
Message-ID: <20150324154623.07cfe557@urahara> (raw)
In-Reply-To: <1af5314868a14e738b049319dc2c21102134bc9b.1426669396.git.daniel@iogearbox.net>
On Wed, 18 Mar 2015 10:13:34 +0100
Daniel Borkmann <daniel@iogearbox.net> wrote:
> Next argument after the tc opcode/verdict is optional, using NEXT_ARG()
> requires to have another argument after that one otherwise tc will bail
> out. Therefore, we need to advance to the next argument manually as done
> elsewhere.
>
> Fixes: 86ab59a6660f ("tc: add support for BPF based actions")
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Applied (to master).
prev parent reply other threads:[~2015-03-24 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 9:13 [PATCH iproute2] tc: m_bpf: fix next arg selection after tc opcode Daniel Borkmann
2015-03-18 10:00 ` Jiri Pirko
2015-03-18 10:02 ` Daniel Borkmann
2015-03-18 10:13 ` Jiri Pirko
2015-03-24 22:46 ` 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=20150324154623.07cfe557@urahara \
--to=stephen@networkplumber.org \
--cc=daniel@iogearbox.net \
--cc=jhs@mojatatu.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 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).