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: <CAFLxGvweL_O16TwvERsMSwf1UPa5BFwSyFNNRu6Z1CD4ExZXSg@mail.gmail.com>
Date:	Sun, 22 Sep 2013 20:23:18 +0200
From:	richard -rw- weinberger <richard.weinberger@...il.com>
To:	Markus Elfring <Markus.Elfring@....de>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Would an "information module" be useful?

On Sun, Sep 22, 2013 at 7:05 PM, Markus Elfring <Markus.Elfring@....de> wrote:
> Hello,
>
> I became interested in an use case where I want to pass customised data from the
> boot command-line to other user processes. I have read the available
> documentation in the way that kernel modules provide such a means to get
> additional parameters recorded.
>
> I have got the understanding that a kernel module provides also a name space for
> such boot parameters. (Are they also called "attributes" there?)
> Now I would be interested to create a module for my needs so that the passed
> data will be stored in the sys file system. Which software component is
> responsible for this task?
>
> I find that another implementation detail needs more clarification. The modules
> usually drive some hardware.
> https://www.kernel.org/doc/Documentation/filesystems/sysfs.txt
>
> But I am looking for a kind of kernel module which does not serve any hardware.
> I imagine that it should be sufficient to register it as a simple information sink.
>
> How do you think about my considerations?
> Would you like to share any alternative ideas?

Why can't you use /proc/cmdline?
systemd for example parses /proc/cmdline by looking at keys like "systemd.*=".
(see parse_proc_cmdline())

-- 
Thanks,
//richard
--
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