netdev - Re: [PATCH v2 net-next] net: filter: fix length calculation in BPF testsuite

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]

Date:	Mon, 02 Jun 2014 16:33:14 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	chema@...gle.com
Cc:	edumazet@...gle.com, dborkman@...hat.com, ast@...mgrid.com,
	netdev@...r.kernel.org
Subject: Re: [PATCH v2 net-next] net: filter: fix length calculation in BPF
 testsuite

From: Chema Gonzalez <chema@...gle.com>
Date: Fri, 30 May 2014 10:15:12 -0700

> The current probe_filter_length() (the function that calculates the
> length of a test BPF filter) behavior is to declare the end of the
> filter as soon as it finds {0, *, *, 0}. This is actually a valid
> insn ("ld #0"), so any filter with includes "BPF_STMT(BPF_LD | BPF_IMM, 0)"
> fails (its length is cut short).
> 
> We are changing probe_filter_length() so as to start from the end, and
> declare the end of the filter as the first instruction which is not
> {0, *, *, 0}. This solution produces a simpler patch than the
> alternative of using an explicit end-of-filter mark. It is technically
> incorrect if your filter ends up with "ld #0", but that should not
> happen anyway.
> 
> We also add a new test (LD_IMM_0) that includes ld #0 (does not work
> without this patch).
> 
> Signed-off-by: Chema Gonzalez <chema@...gle.com>

Applied, thank you.
--
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