[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPhsuW5uu8cOYJWJ3Gne+ixpiWVAby1hZOnUgsXcFASEhV4Xhg@mail.gmail.com>
Date: Fri, 20 Jun 2025 14:59:17 -0700
From: Song Liu <song@...nel.org>
To: bpf@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org,
brauner@...nel.org, Mickaël Salaün <mic@...ikod.net>
Cc: kernel-team@...a.com, andrii@...nel.org, eddyz87@...il.com, ast@...nel.org,
daniel@...earbox.net, martin.lau@...ux.dev, viro@...iv.linux.org.uk,
jack@...e.cz, kpsingh@...nel.org, mattbobrowski@...gle.com, m@...wtm.org,
neil@...wn.name
Subject: Re: [PATCH v5 bpf-next 0/5] bpf path iterator
Hi Christian, Mickaël, and folks,
Could you please share your comments on this version? Does this
look sane?
Thanks,
Song
On Mon, Jun 16, 2025 at 11:11 PM Song Liu <song@...nel.org> wrote:
>
> In security use cases, it is common to apply rules to VFS subtrees.
> However, filtering files in a subtree is not straightforward [1].
>
> One solution to this problem is to start from a path and walk up the VFS
> tree (towards the root). Among in-tree LSMs, Landlock uses this solution.
>
[...]
Powered by blists - more mailing lists