Commit 228b09de authored by Luis Chamberlain's avatar Luis Chamberlain
Browse files

sysctl: clarify register_sysctl_init() base directory order 

Relatively new docs which I added which hinted the base directories needed
to be created before is wrong, remove that incorrect comment. This has been
hinted before by Eric twice already [0] [1], I had just not verified that
until now. Now that I've verified that updates the docs to relax the context
described.

[0] https://lkml.kernel.org/r/875ys0azt8.fsf@email.froward.int.ebiederm.org
[1] https://lkml.kernel.org/r/87ftbiud6s.fsf@x220.int.ebiederm.org



Cc: stable@vger.kernel.org # v5.17
Cc: Christian Brauner <brauner@kernel.org>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>
Suggested-by: default avatarEric W. Biederman <ebiederm@xmission.com>
Signed-off-by: default avatarLuis Chamberlain <mcgrof@kernel.org>
parent b2f56e55

fs/proc/proc_sysctl.c

+1 −4
Original line number Diff line number Diff line
@@ -1440,10 +1440,7 @@ EXPORT_SYMBOL(register_sysctl); 
 * register_sysctl() failing on init are extremely low, and so for both reasons

 * this function does not return any error as it is used by initialization code.

 *

 * Context: Can only be called after your respective sysctl base path has been

 * registered. So for instance, most base directories are registered early on

 * init before init levels are processed through proc_sys_init() and

 * sysctl_init_bases().

 * Context: if your base directory does not exist it will be created for you.

 */

void __init __register_sysctl_init(const char *path, struct ctl_table *table,

				 const char *table_name)