linux-kernel - Command line parameter not passed to module in linux-next

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: <20090227170105.GA22304@schmichrtp.de.ibm.com>
Date:	Fri, 27 Feb 2009 18:01:05 +0100
From:	Christof Schmitt <christof.schmitt@...ibm.com>
To:	linux-kernel@...r.kernel.org, rusty@...tcorp.com.au
Subject: Command line parameter not passed to module in linux-next

The linux-next kernel does not pass charp parameters from the kernel
command line to modules:

# cat /proc/cmdline 
dasd=4d70-4d73 root=/dev/dasdc1 zfcp.device=0.0.181d,0x500507630310c562,0x401040C300000000 zfcp.dbfsize=4096  BOOT_IMAGE=0 

# cat /sys/module/zfcp/parameters/device 
<NULL>

It seems that this patches introduces the problem:
	commit 9f229de63cf02297c0e0fbaa8d74b962cceff435
	Author: Rusty Russell <rusty@...tcorp.com.au>
	Date:   Fri Feb 20 10:31:19 2009 +1100

	    param:fix-charp-sysfs-write

Reverting the patch on linux-next fixes the problem:

# cat /sys/module/zfcp/parameters/device 
0.0.181d,0x500507630310c562,0x401040C300000000

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