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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 18 Mar 2015 11:02:54 +0100
From:	Daniel Borkmann <daniel@...earbox.net>
To:	Jiri Pirko <jiri@...nulli.us>
CC:	stephen@...workplumber.org, jhs@...atatu.com,
	netdev@...r.kernel.org
Subject: Re: [PATCH iproute2] tc: m_bpf: fix next arg selection after tc opcode

On 03/18/2015 11:00 AM, Jiri Pirko wrote:
> Wed, Mar 18, 2015 at 10:13:34AM CET, 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>
>
> Thanks for fixing this Daniel.

Thanks & sorry I forgot to put you in Cc, I realized that too late.

Lack of coffee. ;)
--
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