| 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
| ||
|
Message-Id: <20070905100916.f8e31bff.randy.dunlap@oracle.com> Date: Wed, 5 Sep 2007 10:09:16 -0700 From: Randy Dunlap <randy.dunlap@...cle.com> To: Justin Piszcz <jpiszcz@...idpixels.com> Cc: linux-kernel@...r.kernel.org Subject: Re: modinfo <modulename> question On Wed, 5 Sep 2007 12:34:13 -0400 (EDT) Justin Piszcz wrote: > Is there anyway to get/see what parameters were passed to a kernel module? > Running modinfo -p <module> will show the defaults, but for example, st, > the scsi tape driver, is there a way to see what it is currently using? I > know in dmesg it shows this when you load it initially (but if say dmesg > has been cleared or the buffer was filled up)? If a "module" (whether built as a loadable module or builtin to the kernel image) uses module_param() with a permission (or mode) field that allows reading that parameter, then the parameter will show up in /sys/module/<module>/parameters/<parameter>. E.g., drivers/scsi/sg has these parameters listed and are readable by anyone: -rw-r--r-- 1 root root 4096 Sep 5 10:07 allow_dio -rw-r--r-- 1 root root 4096 Sep 5 10:07 def_reserved_size -rw-r--r-- 1 root root 4096 Sep 5 10:07 scatter_elem_sz However, the st driver uses 0 for permission (mode), so none of its parameters is visible. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** - 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/
Powered by blists - more mailing lists