linux-kernel - Re: Some kernel module options not showing up in modinfo

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

Date:	Fri, 22 Nov 2013 13:06:46 +1030
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Raphael Hertzog <hertzog@...ian.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Some kernel module options not showing up in modinfo

Raphael Hertzog <hertzog@...ian.org> writes:
> Hello,
>
> I noticed that some options are not visible in the modinfo output. For
> instance "modinfo lockd" reports this on my Debian sid system:
>
> $ modinfo lockd
> filename:       /lib/modules/3.11-1-amd64/kernel/fs/lockd/lockd.ko
> license:        GPL
> description:    NFS file locking service version 0.5.
> author:         Olaf Kirch <okir@...ad.swb.de>
> depends:        sunrpc
> intree:         Y
> vermagic:       3.11-1-amd64 SMP mod_unload modversions 
> parm:           nsm_use_hostnames:bool
> parm:           nlm_max_connections:uint
> $
>
> Yet I know that there are more options and the kernel source code confirms
> this:
> http://lxr.free-electrons.com/source/fs/lockd/svc.c#L569
>
> Multiple other options are defined by way of module_param_call(...) like
> nlm_grace_period, nlm_timeout, nlm_updport, nlm_tcpport.
>
> Ben Hutchings (one of the Debian kernel maintainers) confirmed me that
> this was unexpected and suggested me to report it to you. If you have any
> questions, just ask.

Yes, the module_param() macro adds a type description.  The
module_param_call() does not.

Hope that helps,
Rusty.
--
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/