[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230530232914.3689712-1-mcgrof@kernel.org>
Date: Tue, 30 May 2023 16:29:12 -0700
From: Luis Chamberlain <mcgrof@...nel.org>
To: keescook@...omium.org, yzaikin@...gle.com, dhowells@...hat.com,
jarkko@...nel.org, paul@...l-moore.com, jmorris@...ei.org,
serge@...lyn.com, j.granados@...sung.com, brauner@...nel.org
Cc: ebiederm@...ssion.com, patches@...ts.linux.dev,
linux-fsdevel@...r.kernel.org, keyrings@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, Luis Chamberlain <mcgrof@...nel.org>
Subject: [PATCH 0/2] sysctl: move umh and keys sysctls
If you look at kernel/sysctl.c there are two sysctl arrays which
are declared in header files but registered with no good reason now
on kernel/sysctl.c instead of the place they belong. So just do
the registration where it belongs.
The penalty of this is just 66 bytes for moving both registrations
to its own file, but soon we'll be removing all sysctl empty entries
at each array, and we've already done tons of cleanup on fs/proc/proc_sysctl.c
which saved us hundreds of bytes so we have few karma points.
With this, we no now only have two sysctl arrays left to start clearing
up the kernel one and the vm one.
Luis Chamberlain (2):
sysctl: move umh sysctl registration to its own file
sysctl: move security keys sysctl registration to its own file
include/linux/key.h | 3 ---
include/linux/umh.h | 2 --
kernel/sysctl.c | 5 -----
kernel/umh.c | 11 ++++++++++-
security/keys/sysctl.c | 7 +++++++
5 files changed, 17 insertions(+), 11 deletions(-)
--
2.39.2
Powered by blists - more mailing lists