From: Luis Chamberlain <mcgrof@kernel.org>
To: akpm@linux-foundation.org, viro@zeniv.linux.org.uk,
keescook@chromium.org, yzaikin@google.com, nixiaoming@huawei.com,
ebiederm@xmission.com, steve@sk2.org,
mcgrof@bombadil.infradead.org, mcgrof@kernel.org,
andriy.shevchenko@linux.intel.com, jlayton@kernel.org,
bfields@fieldses.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/9] sysctl: 4th set of kernel/sysctl cleanups
Date: Mon, 29 Nov 2021 12:55:39 -0800 [thread overview]
Message-ID: <20211129205548.605569-1-mcgrof@kernel.org> (raw)
This is the 4th set of kernel/sysctl.c cleanups. These are being
pushed out for review for the first time. This is trying to move all
filesystem sysctl knobs out from kernel/sysctl.c to where they are
actually being used.
This is slimming down the fs uses of kernel/sysctl.c to the point
that the next step is to just get rid of the fs base directory for it
and move that elsehwere, so that next patch series starts dealing with
that to demo how we can end up cleaning up a full base directory from
kernel/sysctl.c, one at a time.
Luis Chamberlain (9):
fs: move inode sysctls to its own file
fs: move fs stat sysctls to file_table.c
fs: move dcache sysctls to its own file
sysctl: move maxolduid as a sysctl specific const
fs: move shared sysctls to fs/sysctls.c
fs: move locking sysctls where they are used
fs: move namei sysctls to its own file
fs: move fs/exec.c sysctls into its own file
fs: move pipe sysctls to is own file
fs/Makefile | 1 +
fs/dcache.c | 32 ++++-
fs/exec.c | 90 ++++++++++++++
fs/file_table.c | 47 +++++--
fs/inode.c | 31 ++++-
fs/locks.c | 34 ++++-
fs/namei.c | 58 ++++++++-
fs/pipe.c | 64 +++++++++-
fs/proc/proc_sysctl.c | 2 +-
fs/sysctls.c | 38 ++++++
include/linux/dcache.h | 10 --
include/linux/fs.h | 13 --
include/linux/pipe_fs_i.h | 4 -
include/linux/sysctl.h | 9 ++
kernel/sysctl.c | 255 ++------------------------------------
15 files changed, 390 insertions(+), 298 deletions(-)
create mode 100644 fs/sysctls.c
--
2.33.0
next reply other threads:[~2021-11-29 22:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 20:55 Luis Chamberlain [this message]
2021-11-29 20:55 ` [PATCH 1/9] fs: move inode sysctls to its own file Luis Chamberlain
2021-11-29 20:55 ` [PATCH 2/9] fs: move fs stat sysctls to file_table.c Luis Chamberlain
2021-11-29 20:55 ` [PATCH 3/9] fs: move dcache sysctls to its own file Luis Chamberlain
2021-11-29 20:55 ` [PATCH 4/9] sysctl: move maxolduid as a sysctl specific const Luis Chamberlain
2021-12-17 16:15 ` Mickaël Salaün
2021-12-20 19:25 ` Luis Chamberlain
2021-12-30 0:46 ` Andrew Morton
2021-12-30 11:24 ` Mickaël Salaün
2021-11-29 20:55 ` [PATCH 5/9] fs: move shared sysctls to fs/sysctls.c Luis Chamberlain
2021-11-29 20:55 ` [PATCH 6/9] fs: move locking sysctls where they are used Luis Chamberlain
2021-11-29 20:55 ` [PATCH 7/9] fs: move namei sysctls to its own file Luis Chamberlain
2021-11-29 20:55 ` [PATCH 8/9] fs: move fs/exec.c sysctls into " Luis Chamberlain
2021-11-29 20:55 ` [PATCH 9/9] fs: move pipe sysctls to is " 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=20211129205548.605569-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bfields@fieldses.org \
--cc=ebiederm@xmission.com \
--cc=jlayton@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@bombadil.infradead.org \
--cc=nixiaoming@huawei.com \
--cc=steve@sk2.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.