[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200406124740.GS23230@ZenIV.linux.org.uk>
Date: Mon, 6 Apr 2020 13:47:40 +0100
From: Al Viro <viro@...iv.linux.org.uk>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Jiri Olsa <jolsa@...nel.org>, Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>, netdev@...r.kernel.org,
bpf@...r.kernel.org, Yonghong Song <yhs@...com>,
Martin KaFai Lau <kafai@...com>,
David Miller <davem@...hat.com>,
John Fastabend <john.fastabend@...il.com>,
Jesper Dangaard Brouer <hawk@...nel.org>,
Wenbo Zhang <ethercflow@...il.com>,
KP Singh <kpsingh@...omium.org>,
Andrii Nakryiko <andriin@...com>, bgregg@...flix.com
Subject: Re: [RFC 0/3] bpf: Add d_path helper
On Mon, Apr 06, 2020 at 11:09:18AM +0200, Jiri Olsa wrote:
> it could be called as bpf helper from any place we could put
> the trampoline probe on.. so most of the kernel functions
> (at entry or exit) .. we can make checks, like for context
> before we allow to call it
Hard NAK, then. If you can insert its call at the entry to
e.g. umount_tree(), you will get deadlocks. The same for e.g.
select_collect() (same effect on a different seqlock).
Powered by blists - more mailing lists