linux-kernel - Re: Checking module parameters

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-prev] [day] [month] [year] [list]

Date:	Mon, 19 Jan 2009 14:06:34 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Nick Craig-Wood <nick@...ig-wood.com>
CC:	David Wagner <daw@...berkeley.edu>, linux-kernel@...r.kernel.org
Subject: Re: Checking module parameters

Nick Craig-Wood wrote:
> On Mon, Jan 19, 2009 at 11:19:34AM +0100, Stefan Richter wrote:
>> There is also /sys/module/*/parameters/* which can be read and in some
>> cases even be written.
> 
> It doesn't appear to show the force parameter.

You are right.
>From drivers/ata/libata-core.c:

|> static char ata_force_param_buf[PAGE_SIZE] __initdata;
|> /* param_buf is thrown away after initialization, disallow read */
|> module_param_string(force, ata_force_param_buf,
sizeof(ata_force_param_buf), 0);
|> MODULE_PARM_DESC(force, "Force ATA configurations including cable
type, link speed and transfer mode (see
Documentation/kernel-parameters.txt for details)");

The 0 in module_param_string are the sysfs file permissions of libata.force.

And __initdata means that the memory goes away after ata_init() returned.
-- 
Stefan Richter
-=====-==--= ---= =--==
http://arcgraph.de/sr/
--
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/