linux-kernel - Re: [GIT]: Networking

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: <20090106081135.GA12695@uranus.ravnborg.org>
Date:	Tue, 6 Jan 2009 09:11:35 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	David Miller <davem@...emloft.net>
Cc:	jaswinderlinux@...il.com, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, dwmw2@...radead.org
Subject: Re: [GIT]: Networking

On Mon, Jan 05, 2009 at 10:07:42PM -0800, David Miller wrote:
> From: Sam Ravnborg <sam@...nborg.org>
> Date: Tue, 6 Jan 2009 06:51:44 +0100
> 
> > We should avoid a central file and push this information
> > out to the Kconfig files that are at the driver site.
> > 
> > Then we can postprocess autoconf.h to get the filenames etc.
> 
> I'll take this opportunity to once again promote my idea wherein build
> information (and perhaps other bits like firmware info) for a driver
> is encoded into the source of the driver itself, and the build system
> just extracts that stuff into Makefiles and whatnot at build time. :-)

One of the pratical issues I have with this is when to read which files.

What we could do is something like:

- during *config scan all "wildcard enabled" directories
  and read the Kconfig info from the relevant .C files.
- record which .C files which included Kconfig and do
  an automatic "scan + oldconfig" when one of these files
  changes

When we add new Kconfig info to a file we would have
to manually do the *config to trigger a scan for the .C files


In the .C file we should restrict us to the first 100 lines or so
to have the Kconfig info to speedd up the 'parse' for this info.

Something like this:

/* Kconfig
config FOO
	tristate "A self contained driver"
	depends on USB
	source mydriver-debug.c if DEBUG
	modulename foobar
	help
	  This is a driver for ...
*/

The source file where this info is contained is implicit a source
of this module.
And if we can convince the firmware guys then the firmware info could
be included in the same section.


	Sam
--
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/