linux-kernel - Re: + allow-proc-configgz-to-be-built-as-a-module.patch added to -mm tree

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: <d43160c70609151604pfe83b3nc130f2abc250baa6@mail.google.com>
Date:	Fri, 15 Sep 2006 19:04:30 -0400
From:	rossb <rossb@...gle.com>
To:	"Randy.Dunlap" <rdunlap@...otime.net>
Cc:	linux-kernel@...r.kernel.org, akpm@...l.org,
	mm-commits@...r.kernel.org, akpm@...gle.com, sam@...nborg.org
Subject: Re: + allow-proc-configgz-to-be-built-as-a-module.patch added to -mm tree

On 9/15/06, Randy.Dunlap <rdunlap@...otime.net> wrote:
> > In some ways this is a bit risky, because the .config which is used for
> > compiling kernel/configs.c isn't necessarily the same as the .config which was
> > used to build vmlinux.
>
> and that's why a module wasn't allowed.
> It's not worth the risk IMO.

It's not worth the risk for distributions or if you are tyring to
support people building their own kernels.  But if you are in an
environment where you have enough control that you are not worried the
kernel and the module being built at separate times or with different
configs, then it's a nice compromise between convenience and memory
use.

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