linux-kernel - Re: [PATCH 0/3] Implement /proc/built-in file similar to /proc/modules

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: <20140914153832.GC4064@kroah.com>
Date:	Sun, 14 Sep 2014 08:38:32 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Kirill Tkhai <tkhai@...dex.ru>
Cc:	mmarek@...e.cz, arnd@...db.de, linux-kbuild@...r.kernel.org,
	linux-kernel@...r.kernel.org, oleg@...hat.com,
	grant.likely@...retlab.ca, ebiederm@...ssion.com,
	akpm@...ux-foundation.org, ktkhai@...allels.com, sam@...nborg.org
Subject: Re: [PATCH 0/3] Implement /proc/built-in file similar to
 /proc/modules

On Sun, Sep 14, 2014 at 02:18:13PM +0400, Kirill Tkhai wrote:
> This series implements a possibility to show the list of built-in drivers
> to userspace. The names of drivers will be the same as when they are modules.

Have you looked at /sys/modules/ ?  Doesn't that show what you want
here?

> So, if your system has "loop" driver then it appears either in /proc/modules
> or in /proc/built-in and userspace will be able to know about this.
> 
> Now this is impossible. The only way to get kernel configuration is
> /proc/config.gz, but CONFIG_* names can change from time to time. Module
> names are more or less standardized.

Module names aren't "standardized", we change them at times when needed,
just like CONFIG_ names.

What is your end goal here?  As you say, config.gz is the real kernel
configuration, just having a list of modules built in isn't going to
help much in getting a working kernel config without it.

thanks,

greg k-h
--
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/