linux-kernel - [RESEND PATCH] configfs: init configfs module earlier at boot time

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1428422171-3180-1-git-send-email-daniel.baluta@intel.com>
Date:	Tue,  7 Apr 2015 18:56:11 +0300
From:	Daniel Baluta <daniel.baluta@...el.com>
To:	viro@...iv.linux.org.uk, hch@....de, jlbec@...lplan.org
Cc:	linux-fsdevel@...r.kernel.org, lars@...afoo.de,
	daniel.baluta@...el.com, linux-kernel@...r.kernel.org
Subject: [RESEND PATCH] configfs: init configfs module earlier at boot time

We need this earlier in the boot process to allow various subsystems
to use configfs (e.g Industrial IIO).

Also, debugfs is at core_initcall level and configfs should be on
the same level from infrastructure point of view.

Suggested-by: Lars-Peter Clausen <lars@...afoo.de>
Signed-off-by: Daniel Baluta <daniel.baluta@...el.com>
---
* Extended CC list with Al, Christoph and fsdevel :)

 fs/configfs/mount.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/configfs/mount.c b/fs/configfs/mount.c
index da94e41..5373567 100644
--- a/fs/configfs/mount.c
+++ b/fs/configfs/mount.c
@@ -173,5 +173,5 @@ MODULE_LICENSE("GPL");
 MODULE_VERSION("0.0.2");
 MODULE_DESCRIPTION("Simple RAM filesystem for user driven kernel subsystem configuration.");
 
-module_init(configfs_init);
+core_initcall(configfs_init);
 module_exit(configfs_exit);
-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/