netdev - Re: [PATCH iproute2] tc: m_bpf: fix next arg selection after tc opcode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150324154623.07cfe557@urahara>
Date:	Tue, 24 Mar 2015 15:46:23 -0700
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	Daniel Borkmann <daniel@...earbox.net>
Cc:	jhs@...atatu.com, netdev@...r.kernel.org
Subject: Re: [PATCH iproute2] tc: m_bpf: fix next arg selection after tc
 opcode

On Wed, 18 Mar 2015 10:13:34 +0100
Daniel Borkmann <daniel@...earbox.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@...earbox.net>

Applied (to master).
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html