From: Luis Chamberlain <mcgrof@kernel.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
Al Viro <viro@ZenIV.linux.org.uk>,
Kees Cook <keescook@chromium.org>
Cc: Xiaoming Ni <nixiaoming@huawei.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Helge Deller <deller@gmx.de>,
Parisc List <linux-parisc@vger.kernel.org>,
yzaikin@google.com, linux-fsdevel@vger.kernel.org,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: linux-next: manual merge of the vfs tree with the parisc-hd tree
Date: Wed, 13 May 2020 14:14:22 +0000 [thread overview]
Message-ID: <20200513141421.GP11244@42.do-not-panic.com> (raw)
In-Reply-To: <87d078oss9.fsf@x220.int.ebiederm.org>
On Wed, May 13, 2020 at 08:42:30AM -0500, Eric W. Biederman wrote:
> Luis Chamberlain <mcgrof@kernel.org> writes:
>
> > On Tue, May 12, 2020 at 12:40:55PM -0500, Eric W. Biederman wrote:
> >> Luis Chamberlain <mcgrof@kernel.org> writes:
> >>
> >> > On Tue, May 12, 2020 at 06:52:35AM -0500, Eric W. Biederman wrote:
> >> >> Luis Chamberlain <mcgrof@kernel.org> writes:
> >> >>
> >> >> > +static struct ctl_table fs_base_table[] = {
> >> >> > + {
> >> >> > + .procname = "fs",
> >> >> > + .mode = 0555,
> >> >> > + .child = fs_table,
> >> >> > + },
> >> >> > + { }
> >> >> > +};
> >> >> ^^^^^^^^^^^^^^^^^^^^^^^^ You don't need this at all.
> >> >> > > +static int __init fs_procsys_init(void)
> >> >> > +{
> >> >> > + struct ctl_table_header *hdr;
> >> >> > +
> >> >> > + hdr = register_sysctl_table(fs_base_table);
> >> >> ^^^^^^^^^^^^^^^^^^^^^ Please use register_sysctl instead.
> >> >> AKA
> >> >> hdr = register_sysctl("fs", fs_table);
> >> >
> >> > Ah, much cleaner thanks!
> >>
> >> It is my hope you we can get rid of register_sysctl_table one of these
> >> days. It was the original interface but today it is just a
> >> compatibility wrapper.
> >>
> >> I unfortunately ran out of steam last time before I finished converting
> >> everything over.
> >
> > Let's give it one more go. I'll start with the fs stuff.
>
> Just to be clear moving the tables out of kernel/sysctl.c is a related
> but slightly different problem.
Sure, but also before we go on this crusade, how about we add a few
helpers:
register_sysctl_kernel()
register_sysctl_vm()
register_sysctl_fs()
register_sysctl_debug()
register_sysctl_dev()
That should make it easier to look for these, and shorter. We *know*
this is a common path, given the size of the existing table.
> Today it looks like there are 35 calls of register_sysctl_table
> and 9 calls of register_sysctl_paths.
>
> Among them is lib/sysctl_test.c and check-sysctl-docs.
>
> Meanwhile I can only find 5 calls to register_sysctl in the tree
> so it looks like I didn't get very far converting things over.
While we're on the spring cleaning topic, I've tried to put what I can
think of for TODO items here, anything else? Feel free to edit, its a
wiki after all.
https://kernelnewbies.org/KernelProjects/proc
Feel free to add wishlist items.
Luis
next prev parent reply other threads:[~2020-05-13 14:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 1:11 linux-next: manual merge of the vfs tree with the parisc-hd tree Stephen Rothwell
2020-05-11 1:55 ` Xiaoming Ni
2020-05-12 0:33 ` Luis Chamberlain
2020-05-12 5:22 ` Kees Cook
2020-05-12 5:44 ` Luis Chamberlain
2020-05-12 11:52 ` Eric W. Biederman
2020-05-12 17:24 ` Luis Chamberlain
2020-05-12 17:40 ` Eric W. Biederman
2020-05-12 22:03 ` Luis Chamberlain
2020-05-13 4:04 ` Xiaoming Ni
2020-05-13 12:50 ` Luis Chamberlain
2020-05-14 6:05 ` Xiaoming Ni
2020-05-14 16:17 ` Xiaoming Ni
2020-05-15 16:08 ` Luis Chamberlain
2020-05-13 13:42 ` Eric W. Biederman
2020-05-13 14:14 ` Luis Chamberlain [this message]
2020-05-13 14:44 ` Eric W. Biederman
2020-05-13 15:02 ` Luis Chamberlain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200513141421.GP11244@42.do-not-panic.com \
--to=mcgrof@kernel.org \
--cc=deller@gmx.de \
--cc=ebiederm@xmission.com \
--cc=hch@lst.de \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=nixiaoming@huawei.com \
--cc=sfr@canb.auug.org.au \
--cc=viro@ZenIV.linux.org.uk \
--cc=yzaikin@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).