[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20211117033006.qct3ve3tknfy3xy7@garbanzo>
Date: Tue, 16 Nov 2021 19:30:06 -0800
From: Luis Chamberlain <mcgrof@...nel.org>
To: "Eric W. Biederman" <ebiederm@...ssion.com>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: keescook@...omium.org, yzaikin@...gle.com, nixiaoming@...wei.com,
axboe@...nel.dk, clemens@...isch.de, arnd@...db.de,
gregkh@...uxfoundation.org, jani.nikula@...ux.intel.com,
joonas.lahtinen@...ux.intel.com, rodrigo.vivi@...el.com,
airlied@...ux.ie, daniel@...ll.ch, benh@...nel.crashing.org,
rdna@...com, viro@...iv.linux.org.uk, mark@...heh.com,
jlbec@...lplan.org, joseph.qi@...ux.alibaba.com, vbabka@...e.cz,
sfr@...b.auug.org.au, jack@...e.cz, amir73il@...il.com,
rafael@...nel.org, tytso@....edu, julia.lawall@...6.fr,
akpm@...ux-foundation.org, intel-gfx@...ts.freedesktop.org,
dri-devel@...ts.freedesktop.org, linuxppc-dev@...ts.ozlabs.org,
ocfs2-devel@....oracle.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 12/13] sysctl: add helper to register empty subdir
On Fri, May 29, 2020 at 08:03:02AM -0500, Eric W. Biederman wrote:
> Luis Chamberlain <mcgrof@...nel.org> writes:
>
> > The way to create a subdirectory from the base set of directories
> > is a bit obscure, so provide a helper which makes this clear, and
> > also helps remove boiler plate code required to do this work.
>
> I agreee calling:
> register_sysctl("fs/binfmt_misc", sysctl_mount_point)
> is a bit obscure but if you are going to make a wrapper
> please make it the trivial one liner above.
>
> Say something that looks like:
> struct sysctl_header *register_sysctl_mount_point(const char *path)
> {
> return register_sysctl(path, sysctl_mount_point);
> }
>
> And yes please talk about a mount point and not an empty dir, as these
> are permanently empty directories to serve as mount points. There are
> some subtle but important permission checks this allows in the case of
> unprivileged mounts.
>
> Further code like this belong in proc_sysctl.c next to all of the code
> it is related to so that it is easier to see how to refactor the code if
> necessary.
Alrighty, it's been a while since this kernel/sysctl.c kitchen sink
cleanup... so it's time to respin this now that the merge window is
open. I already rebased patches, addressed all input and now just
waiting to fix any compilation errors. I'm going to split the patches
up into real small sets so to ensure we just get this through becauase
getting this in otherwise is going to be hard.
I'd appreciate folk's review once the patches start going out. I think
a hard part will be deciding what tree this should got through.
Luis
Powered by blists - more mailing lists