[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200304151337.GD9984@chromium.org>
Date: Wed, 4 Mar 2020 16:13:37 +0100
From: KP Singh <kpsingh@...omium.org>
To: Andrii Nakryiko <andrii.nakryiko@...il.com>
Cc: linux-security-module@...r.kernel.org,
open list <linux-kernel@...r.kernel.org>,
bpf <bpf@...r.kernel.org>, Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Paul Turner <pjt@...gle.com>, Jann Horn <jannh@...gle.com>,
Florent Revest <revest@...omium.org>,
Brendan Jackman <jackmanb@...omium.org>
Subject: Re: [PATCH bpf-next v2 4/7] bpf: Attachment verification for
BPF_MODIFY_RETURN
On 03-Mär 21:12, Andrii Nakryiko wrote:
> On Tue, Mar 3, 2020 at 5:56 PM KP Singh <kpsingh@...omium.org> wrote:
> >
> > From: KP Singh <kpsingh@...gle.com>
> >
> > - Allow BPF_MODIFY_RETURN attachment only to functions that are:
> >
> > * Whitelisted by for error injection i.e. by checking
> > within_error_injection_list. Similar disucssions happened for the
> > bpf_overrie_return helper.
>
> 2 typos: discussions and bpf_override_return ;)
/me bows his head in shame ;) Fixed.
-KP
>
> >
> > * security hooks, this is expected to be cleaned up with the LSM
> > changes after the KRSI patches introduce the LSM_HOOK macro:
> >
> > https://lore.kernel.org/bpf/20200220175250.10795-1-kpsingh@chromium.org/
> >
> > - The attachment is currently limited to functions that return an int.
> > This can be extended later other types (e.g. PTR).
> >
> > Signed-off-by: KP Singh <kpsingh@...gle.com>
> > ---
>
> Acked-by: Andrii Nakryiko <andriin@...com>
>
> > kernel/bpf/btf.c | 28 ++++++++++++++++++++--------
> > kernel/bpf/verifier.c | 31 +++++++++++++++++++++++++++++++
> > 2 files changed, 51 insertions(+), 8 deletions(-)
> >
>
> [...]
Powered by blists - more mailing lists