From: Rusty Russell <rusty@rustcorp.com.au>
To: Raphael Hertzog <hertzog@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Some kernel module options not showing up in modinfo
Date: Fri, 22 Nov 2013 13:06:46 +1030 [thread overview]
Message-ID: <87li0hyxfl.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20131121144758.GA6515@x230-buxy.home.ouaza.com>
Raphael Hertzog <hertzog@debian.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@monad.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.
next prev parent reply other threads:[~2013-11-22 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 14:47 Some kernel module options not showing up in modinfo Raphael Hertzog
2013-11-22 2:36 ` Rusty Russell [this message]
2013-11-22 7:34 ` Raphael Hertzog
2013-11-30 22:16 ` Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87li0hyxfl.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=hertzog@debian.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.