Re: [RFC PATCH 2/3] add statmnt(2) syscall
From: Christian Brauner <brauner@kernel.org>
Date: 2023-09-26 10:06:13
Also in:
linux-api, linux-fsdevel, linux-man, lkml
From: Christian Brauner <brauner@kernel.org>
Date: 2023-09-26 10:06:13
Also in:
linux-api, linux-fsdevel, linux-man, lkml
On Mon, Sep 25, 2023 at 05:46:59PM +0200, Arnd Bergmann wrote:
On Mon, Sep 25, 2023, at 15:20, Miklos Szeredi wrote:quoted
On Mon, 25 Sept 2023 at 15:19, Christian Brauner [off-list ref] wrote:quoted
quoted
How about passing u64 *?struct statmnt_req { __u64 mnt_id; __u64 mask; }; ?I'm fine with that as well.Yes, this looks fine for the compat syscall purpose. Not sure if losing visibility of the mnt_id and mask in ptrace or seccomp/bpf is a problem though.
It's an information retrieval syscall so there shouldn't be any need to block it and I think that this ship has sailed in general. Container workloads should migrate from seccomp to landlock if they need to filter system calls like this.