linux-kernel - Re: modinfo <modulename> question

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]

Message-ID: <Pine.LNX.4.64.0709061401270.25942@fbirervta.pbzchgretzou.qr>
Date:	Thu, 6 Sep 2007 14:03:13 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
cc:	Andreas Schwab <schwab@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: modinfo <modulename> question


On Sep 5 2007 13:31, Justin Piszcz wrote:
>>
>> > Is there anyway to get/see what parameters were passed to a kernel 
>> > module?

Not really. Even if a module has parameters exported, they may carry 
default values (and hence, don't fulfill the word "passed", as would be 
the case with `modprobe foo` without {{any extra params} union {params 
in /etc/modprobe*}})

>> /sys/module/<module>/parameters
>
> And under 2.4?

/proc/<module-specific-place>. Generally, even less.



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