Skip to contentSkip to conversation

control what kernel modules get loaded into ramdisk

DISCUSSION Dan Horák 2 participants 4 messages Nov 2, 2009 – Nov 3, 2009 3 messages not in the archive

lore
Share & tools
lore

Dan Horák

author
#0 lore raw

Hello,

I started to use dracut for preparing generic ramdisk for Fedora/ARM. The issue with ramdisks on ARM is that they are usually limited in size because they are stored in the internal flash memories whose capacity can be 8 or 16 MB (for kernel, ramdisk and other stuff) in the commercial devices (like NAS from QNAP). So I used the "omit_dracutmodules" option in the config file to drop stuff like i18n, plymouth etc. It works, the created ramdisk is usable, but what remains quite large are the kernel modules for all filesystems. The ability to limit the list of drivers for block devices would be also nice. Is there a way to control what kernel modules get loaded into the ramdisk, like some black- or whitelist?

Thanks

Dan

A message that is not in the archive (sent off-list or not yet received): 1257183267.3755.286.camel-Gu2OudDT4ISyu7giWUE+hA@public.gmane.org

author
#2 lore raw

Dan Horák píše v Po 02. 11. 2009 v 18:34 +0100:

Quoted 10 lines

Hello,

I started to use dracut for preparing generic ramdisk for Fedora/ARM. The issue with ramdisks on ARM is that they are usually limited in size because they are stored in the internal flash memories whose capacity can be 8 or 16 MB (for kernel, ramdisk and other stuff) in the commercial devices (like NAS from QNAP). So I used the "omit_dracutmodules" option in the config file to drop stuff like i18n, plymouth etc. It works, the created ramdisk is usable, but what remains quite large are the kernel modules for all filesystems. The ability to

I have solved the problem with filesystem modules with an introduction of new command line/config file parameter. It controls the list of filesystem modules that will be included when running in generic mode. See the attached patch for details.

Quoted 3 lines

limit the list of drivers for block devices would be also nice. Is there a way to control what kernel modules get loaded into the ramdisk, like some black- or whitelist?

Dan

From c903db8863923a6f9d32f6ac5e5481b74cb1e75c Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Dan=20Hor=C3=A1k?= <[email protected]>
Date: Tue, 3 Nov 2009 10:39:59 +0100
Subject: [PATCH 1/3] specify a list of kernel filesystem modules to be exlusively included in the initramfs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

---
 dracut                                   |    6 +++++-
 dracut.8                                 |    3 +++
 modules.d/90kernel-modules/installkernel |    8 ++++++--
 3 files changed, 14 insertions(+), 3 deletions(-)
dracut +5 -1
index 7b9304f..dbc5d73 100755
@@ -37,6 +37,8 @@ Creates initial ramdisk images for preloading modules
                         exclusively include in the initramfs.
   --add-drivers [LIST]  Specify a space-separated list of kernel 
                         modules to add to the initramfs.
+  --filesystems [LIST]  Specify a space-separated list of filesystem kenrel
+                        modules to exclusively include in the initramfs.
   -k, --kmoddir [DIR]   Specify the directory, where to look for kernel 
                         modules
   --fwdir [DIR]         Specify additional directories, where to look for 
@@ -76,6 +78,7 @@ while (($# > 0)); do
 	-a|--add) add_dracutmodules_l="$2"; shift;;
 	-d|--drivers) drivers_l="$2"; shift;;
 	--add-drivers) add_drivers_l="$2"; shift;;
+	--filesystems) filesystems_l="$2"; shift;;
 	-k|--kmoddir) drivers_dir_l="$2"; shift;;
 	--fwdir) fw_dir_l="$2"; shift;;
 	--kernel-only) kernel_only="yes"; nokernel="no";;
@@ -127,6 +130,7 @@ fi
 [[ $add_dracutmodules_l ]] && add_dracutmodules="$add_dracutmodules $add_dracutmodules_l"
 [[ $drivers_l ]] && drivers=$drivers_l
 [[ $add_drivers_l ]] && add_drivers=$add_drivers_l
+[[ $filesystems_l ]] && filesystems=$filesystems_l
 [[ $drivers_dir_l ]] && drivers_dir=$drivers_dir_l
 [[ $fw_dir_l ]] && fw_dir=$fw_dir_l
 [[ $do_strip_l ]] && do_strip=$do_strip_l
@@ -180,7 +184,7 @@ chmod 755 "$initdir"
 
 export initdir hookdirs dracutbasedir dracutmodules drivers \
     fw_dir drivers_dir debug beverbose no_kernel kernel_only \
-    add_drivers mdadmconf lvmconf
+    add_drivers mdadmconf lvmconf filesystems
 
 if [[ $kernel_only != yes ]]; then
     # Create some directory structure first
dracut.8 +3 -0
index 309d0dd..93dafc9 100644
@@ -32,6 +32,9 @@ specify a space-separated list of kernel modules to exclusively include in the i
 .BR \-\-add-drivers " \fILIST\fR"
 specify a space-separated list of kernel modules to add to the initramfs.
 .TP
+.BR \-\-filesystems " \fILIST\fR"
+specify a space-separated list of kernel filesystem modules to exclusively include in the initramfs.
+.TP
 .BR \-k ", " \-\-kmoddir " \fI{DIR}\fR   
 specify the directory, where to look for kernel modules
 .TP
modules.d/90kernel-modules/installkernel +6 -2
index b5e4c93..77fbe09 100755
@@ -6,9 +6,13 @@ if [[ -z $drivers ]]; then
 	 nm -uPA "$1" | egrep -q "$blockfuncs"
     }
     instmods pcmcia sd_mod $(filter_kernel_modules block_module_test) "=drivers/pcmcia" =ide
-    # if not on hostonly mode, install all known filesystems.
+    # if not on hostonly mode, install all known filesystems if the required list is not set via the filesystems variable
     if [[ $hostonly = '' ]]; then
-	instmods '=fs'
+	if [[ -z $filesystems ]]; then
+	    instmods '=fs'
+	else
+	    instmods $filesystems
+	fi
     else
 	instmods $(get_fs_type "/dev/block/$(find_root_block_device)")
     fi
Signature · 15 lines
1.6.3.3

From d9912f909196d7d53981720b444d1aa23d1edbe6 Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Dan=20Hor=C3=A1k?= <[email protected]>
Date: Tue, 3 Nov 2009 11:05:12 +0100
Subject: [PATCH 2/3] add the "filesystems" option into config file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit


Signed-off-by: Dan Horák <[email protected]>
---
 dracut.conf |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)
dracut.conf +3 -0
index 2ebeeda..44cecaf 100644
@@ -9,6 +9,9 @@
 # additional kernel modules to the default
 #add_drivers=""
 
+# list of kernel filesystem modules to be loaded into generic initramfs
+#filesystems=""
+
 # build initrd only to boot current hardware
 #hostonly="-h"
 #
Signature · 15 lines
1.6.3.3

From 80fe42e3224d4240319ddf56ea3deb807ab1e9aa Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Dan=20Hor=C3=A1k?= <[email protected]>
Date: Tue, 3 Nov 2009 11:06:38 +0100
Subject: [PATCH 3/3] append the filesystems list to the exclusive list of kernel modules
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit


Signed-off-by: Dan Horák <[email protected]>
---
 modules.d/90kernel-modules/installkernel |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
modules.d/90kernel-modules/installkernel +1 -1
index 77fbe09..c739bfc 100755
@@ -19,7 +19,7 @@ if [[ -z $drivers ]]; then
     # hardcoded list of exceptions
     rm -fr ${initdir}/lib/modules/*/kernel/fs/ocfs2
 else
-  instmods $drivers
+  instmods $drivers $filesystems
 fi
 
 [[ $add_drivers ]] && instmods $add_drivers
Signature · 1 line
1.6.3.3

A message that is not in the archive (sent off-list or not yet received): [email protected]

#4 lore raw
Quoted 17 lines · Dan Horák

Dan Horák píše v Po 02. 11. 2009 v 18:34 +0100:

Quoted 10 lines

Hello,

I started to use dracut for preparing generic ramdisk for Fedora/ARM. The issue with ramdisks on ARM is that they are usually limited in size because they are stored in the internal flash memories whose capacity can be 8 or 16 MB (for kernel, ramdisk and other stuff) in the commercial devices (like NAS from QNAP). So I used the "omit_dracutmodules" option in the config file to drop stuff like i18n, plymouth etc. It works, the created ramdisk is usable, but what remains quite large are the kernel modules for all filesystems. The ability to

I have solved the problem with filesystem modules with an introduction of new command line/config file parameter. It controls the list of filesystem modules that will be included when running in generic mode. See the attached patch for details.

Quoted 7 lines
Quoted 3 lines

limit the list of drivers for block devices would be also nice. Is there a way to control what kernel modules get loaded into the ramdisk, like some black- or whitelist?

Dan

s/kenrel/kernel/

s/modules to be loaded into generic initramfs/modules to be included in the generic initramfs/

A message that is not in the archive (sent off-list or not yet received): [email protected]

author
#6 lore raw

Harald Hoyer píše v Út 03. 11. 2009 v 11:30 +0100:

Quoted 10 lines
Quoted 10 lines

I have solved the problem with filesystem modules with an introduction of new command line/config file parameter. It controls the list of filesystem modules that will be included when running in generic mode. See the attached patch for details.

Quoted 3 lines

limit the list of drivers for block devices would be also nice. Is there a way to control what kernel modules get loaded into the ramdisk, like some black- or whitelist?

Quoted 7 lines
Quoted 2 lines

Dan

s/kenrel/kernel/

s/modules to be loaded into generic initramfs/modules to be included in the generic initramfs/

updated and joined into 1 commit with better description

Dan

From e67c382bd883ef6b567933b4800c135fd62c8244 Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Dan=20Hor=C3=A1k?= <[email protected]>
Date: Tue, 3 Nov 2009 11:50:55 +0100
Subject: [PATCH] control filesystems included in the generic initramfs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

New "filesystems" command line/config file option is added with the ability to control the list of kernel filesystem modules that are included in the generic initramfs.

---
 dracut                                   |    7 ++++++-
 dracut.8                                 |    3 +++
 dracut.conf                              |    3 +++
 modules.d/90kernel-modules/installkernel |   10 +++++++---
 4 files changed, 19 insertions(+), 4 deletions(-)
dracut +6 -1
index 7b9304f..1954177 100755
@@ -37,6 +37,9 @@ Creates initial ramdisk images for preloading modules
                         exclusively include in the initramfs.
   --add-drivers [LIST]  Specify a space-separated list of kernel 
                         modules to add to the initramfs.
+  --filesystems [LIST]  Specify a space-separated list of kernel filesystem
+                        modules to exclusively include in the generic
+                        initramfs.
   -k, --kmoddir [DIR]   Specify the directory, where to look for kernel 
                         modules
   --fwdir [DIR]         Specify additional directories, where to look for 
@@ -76,6 +79,7 @@ while (($# > 0)); do
 	-a|--add) add_dracutmodules_l="$2"; shift;;
 	-d|--drivers) drivers_l="$2"; shift;;
 	--add-drivers) add_drivers_l="$2"; shift;;
+	--filesystems) filesystems_l="$2"; shift;;
 	-k|--kmoddir) drivers_dir_l="$2"; shift;;
 	--fwdir) fw_dir_l="$2"; shift;;
 	--kernel-only) kernel_only="yes"; nokernel="no";;
@@ -127,6 +131,7 @@ fi
 [[ $add_dracutmodules_l ]] && add_dracutmodules="$add_dracutmodules $add_dracutmodules_l"
 [[ $drivers_l ]] && drivers=$drivers_l
 [[ $add_drivers_l ]] && add_drivers=$add_drivers_l
+[[ $filesystems_l ]] && filesystems=$filesystems_l
 [[ $drivers_dir_l ]] && drivers_dir=$drivers_dir_l
 [[ $fw_dir_l ]] && fw_dir=$fw_dir_l
 [[ $do_strip_l ]] && do_strip=$do_strip_l
@@ -180,7 +185,7 @@ chmod 755 "$initdir"
 
 export initdir hookdirs dracutbasedir dracutmodules drivers \
     fw_dir drivers_dir debug beverbose no_kernel kernel_only \
-    add_drivers mdadmconf lvmconf
+    add_drivers mdadmconf lvmconf filesystems
 
 if [[ $kernel_only != yes ]]; then
     # Create some directory structure first
dracut.8 +3 -0
index 309d0dd..6dc90ad 100644
@@ -32,6 +32,9 @@ specify a space-separated list of kernel modules to exclusively include in the i
 .BR \-\-add-drivers " \fILIST\fR"
 specify a space-separated list of kernel modules to add to the initramfs.
 .TP
+.BR \-\-filesystems " \fILIST\fR"
+specify a space-separated list of kernel filesystem modules to exclusively include in the generic initramfs.
+.TP
 .BR \-k ", " \-\-kmoddir " \fI{DIR}\fR   
 specify the directory, where to look for kernel modules
 .TP
dracut.conf +3 -0
index 2ebeeda..8c8db21 100644
@@ -9,6 +9,9 @@
 # additional kernel modules to the default
 #add_drivers=""
 
+# list of kernel filesystem modules to be included in the generic initramfs
+#filesystems=""
+
 # build initrd only to boot current hardware
 #hostonly="-h"
 #
modules.d/90kernel-modules/installkernel +7 -3
index b5e4c93..c739bfc 100755
@@ -6,16 +6,20 @@ if [[ -z $drivers ]]; then
 	 nm -uPA "$1" | egrep -q "$blockfuncs"
     }
     instmods pcmcia sd_mod $(filter_kernel_modules block_module_test) "=drivers/pcmcia" =ide
-    # if not on hostonly mode, install all known filesystems.
+    # if not on hostonly mode, install all known filesystems if the required list is not set via the filesystems variable
     if [[ $hostonly = '' ]]; then
-	instmods '=fs'
+	if [[ -z $filesystems ]]; then
+	    instmods '=fs'
+	else
+	    instmods $filesystems
+	fi
     else
 	instmods $(get_fs_type "/dev/block/$(find_root_block_device)")
     fi
     # hardcoded list of exceptions
     rm -fr ${initdir}/lib/modules/*/kernel/fs/ocfs2
 else
-  instmods $drivers
+  instmods $drivers $filesystems
 fi
 
 [[ $add_drivers ]] && instmods $add_drivers
Signature · 1 line
1.6.3.3