linux-kernel - Re: [PATCH v2] ARM: net: add JIT support for loads from struct seccomp

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]

Message-Id: <20150509.222858.26253293963482182.davem@davemloft.net>
Date:	Sat, 09 May 2015 22:28:58 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	nschichan@...ebox.fr
Cc:	linux@....linux.org.uk, dborkman@...hat.com, ast@...mgrid.com,
	mgherzan@...il.com, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH v2] ARM: net: add JIT support for loads from struct
 seccomp_data.

From: Nicolas Schichan <nschichan@...ebox.fr>
Date: Thu,  7 May 2015 15:00:13 +0200

> Signed-off-by: Nicolas Schichan <nschichan@...ebox.fr>
> ---
> 
> This patch was first sent as part of a serie modifying the core
> seccomp code to allow the use of the classic BPF JIT. As the core
> changes have been submitted to netdev by Daniel Borkmann, it is now
> time to re-submit this patch separately.
> 
> While not physically dependent of the core seccomp changes they are
> needed for the code added in this patch to be triggered.

Where would you like this to be applied, my tree?

This is an ongoing situation, where people have traditionally not
consistently wanted bpf JIT patches to go into the networking tree.

So I beg everyone posting such things to netdev to be _clear_
and _explicit_ about whether you expect me to integrate the patch
or not.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/