linux-kernel - [PATCH 2/2] brd: RAM block module is called 'brd'

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]

Date:	Tue, 21 Aug 2012 17:10:37 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Nick Piggin <npiggin@...nel.dk>
Cc:	linux-kernel@...r.kernel.org
Subject: [PATCH 2/2] brd: RAM block module is called 'brd'

The RAM block module is called 'brd' ever since commit
9db5579be4bb5320c3248f6acf807aedf05ae143 ("rewrite rd"). Update its
Kconfig entry accordingly.

Signed-off-by: Paul Bolle <pebolle@...cali.nl>
---
0) Of course this driver does have an 'rd' alias, see commit
efedf51c866130945b5db755cb58670e60205d83 ("Add 'rd' alias to new brd
ramdisk driver"). But its name is 'brd'.

1) "modprobe rd" doesn't work anymore under Fedora 16, because of
dracut:
    brd: Unknown parameter `md'

See man 7 dracut.cmdline for all cmdline parameters that can trigger
this error.

2) "modinfo rd" doesn't work. Apparently one needs to feed modinfo the
actual module name and not an alias. Is that by design?

 drivers/block/Kconfig |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
index 2fd52ef..0899d5a 100644
--- a/drivers/block/Kconfig
+++ b/drivers/block/Kconfig
@@ -376,7 +376,7 @@ config BLK_DEV_RAM
 	  during the initial install of Linux.
 
 	  To compile this driver as a module, choose M here: the
-	  module will be called rd.
+	  module will be called brd.
 
 	  Most normal users won't need the RAM disk functionality, and can
 	  thus say N here.
-- 
1.7.7.6

--
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/