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: Mon, 23 Mar 2020 15:12:57 -0700 From: Kees Cook <keescook@...omium.org> To: Casey Schaufler <casey@...aufler-ca.com> Cc: KP Singh <kpsingh@...omium.org>, linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org, Brendan Jackman <jackmanb@...gle.com>, Florent Revest <revest@...gle.com>, Alexei Starovoitov <ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>, James Morris <jmorris@...ei.org>, Paul Turner <pjt@...gle.com>, Jann Horn <jannh@...gle.com>, Florent Revest <revest@...omium.org>, Brendan Jackman <jackmanb@...omium.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: Re: [PATCH bpf-next v5 5/7] bpf: lsm: Initialize the BPF LSM hooks On Mon, Mar 23, 2020 at 02:58:18PM -0700, Casey Schaufler wrote: > That's not too terrible, I suppose. What would you be thinking for > the calls that do use call_int_hook()? > > rc = call_int_hook(something, something_default, goodnesses); > > or embedded in the macro: > > rc = call_int_hook(something, goodnesses); Oh yes, good point. The hook call already knows the name, so: #define call_int_hook(FUNC, ...) ({ \ int RC = FUNC#_default; \ ... -- Kees Cook
Powered by blists - more mailing lists