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]
Message-ID: <AANLkTi=_iawjarxDF8wghrmN4uZ4oFNYeX_K-sqk0ZBO@mail.gmail.com>
Date:	Mon, 1 Nov 2010 21:42:39 +0800
From:	tingwei liu <tingw.liu@...il.com>
To:	Américo Wang <xiyou.wangcong@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: How many params can be accept by kernel module at most?

2010/11/1 Américo Wang <xiyou.wangcong@...il.com>:
> On Mon, Nov 01, 2010 at 05:49:53PM +0800, tingwei liu wrote:
>>The params are transferred by command line. And the params are all in
>>program statically. So the stack size determine the params number. For
>>example: stack size is 4K,and params are unsigned int type with 4
>>bytes,so the max number of params is 1 thousand。
>>
>
> Please don't top-reply.
>
> That is not true, the parameters are passed via 'uargs' of init_module()
> dynamically, this is when you invoke modprobe/insmod.
>
> For your own kernel module, you may use module_param() to provide
> parameters, the max of this is limited to the size of ELF section size,
> since they are stored in "__param" section.
>

I really use module_param() to provide parameters. How much of the ELF
section size? How can I find the document of the ELF.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ