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
| ||
|
Date: Fri, 1 Dec 2017 04:54:39 +0000 From: Al Viro <viro@...IV.linux.org.uk> To: Kees Cook <keescook@...omium.org> Cc: Shmulik Ladkani <shmulik.ladkani@...il.com>, Willem de Bruijn <willemb@...gle.com>, Daniel Borkmann <daniel@...earbox.net>, Pablo Neira Ayuso <pablo@...filter.org>, Linus Torvalds <torvalds@...ux-foundation.org>, David Miller <davem@...emloft.net>, LKML <linux-kernel@...r.kernel.org>, Network Development <netdev@...r.kernel.org>, Christoph Hellwig <hch@...radead.org>, Thomas Garnier <thgarnie@...gle.com>, Jann Horn <jannh@...gle.com> Subject: Re: netfilter: xt_bpf: Fix XT_BPF_MODE_FD_PINNED mode of 'xt_bpf_info_v1' On Fri, Dec 01, 2017 at 03:48:59AM +0000, Al Viro wrote: > Something similar to get_prog_path_type() above might make for a usable > primitive, IMO... Incidentally, bpf_obj_get_user()/bpf_obj_do_get() should just use user_path(), rather than wanking with getname()+kern_path(pname->name)+putname(). Note that kern_path() will do getname_kernel() to get struct pathname... Would cause problems for tracepoints in there, though. And that, BTW, is precisely why I don't want tracepoints in core VFS, TYVM - makes restructuring the code harder...
Powered by blists - more mailing lists