From: Adrian Bunk <bunk@stusta.de>
To: rossb <rossb@google.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org, akpm@osdl.org,
mm-commits@vger.kernel.org, akpm@google.com, sam@ravnborg.org
Subject: Re: + allow-proc-configgz-to-be-built-as-a-module.patch added to -mm tree
Date: Sun, 17 Sep 2006 03:13:52 +0200 [thread overview]
Message-ID: <20060917011352.GM669@stusta.de> (raw)
In-Reply-To: <d43160c70609161748n2af1c88cx33344e7da3e2b302@mail.google.com>
On Sat, Sep 16, 2006 at 08:48:26PM -0400, rossb wrote:
> On 9/16/06, Arjan van de Ven <arjan@infradead.org> 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.
>
> The problem is, the patch is basically s/bool/tristate/ so you can't
> really count on /proc/config.gz anyway. It's a lot like security
> through obscurity.
>
> >One hack we could do is make an md5sum or similar of the config and
> >stick that somewhere which is built in and always available (proc or
> >sysfs or something like that); that can be used to validate any config
> >basically to be "correct matching". In fact we could even make it
> >(optionally) part of the VERMAGIC to avoid any kind of mismatch at all.
>
> Not a bad idea, but I think you want to be able to edit your config
> before compiling modules. In particular, you might want to turn
> something from off to module.
>
> How about we embed the md5sum of the config in the kernel, make it
> available via /proc or /sysfs and then have /proc/config.gz return an
> error in the event the md5sum doesn't match?
IMHO this all sounds like overdesigning something that is only a quick
hack that is sometimes handy:
If you don't want to waste kernel memory, set CONFIG_IKCONFIG=n.
If you are building a kernel for a distribution kernel, set
CONFIG_IKCONFIG=n and place the .config in /boot/config-*
(or a similar place).
We don't need a sophisticated well-defined semantics for the case when
the .config changes due to additional modules selected or other special
cases.
> Ross
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-09-17 1:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200609152158.k8FLw7ud018089@shell0.pdx.osdl.net>
2006-09-15 22:47 ` + allow-proc-configgz-to-be-built-as-a-module.patch added to -mm tree Randy.Dunlap
2006-09-15 23:04 ` rossb
2006-09-15 23:11 ` Randy.Dunlap
2006-09-15 23:41 ` Andrew Morton
2006-09-16 0:14 ` Randy.Dunlap
2006-09-16 0:23 ` Olivier Galibert
2006-09-16 0:33 ` Adrian Bunk
2006-10-02 1:17 ` Randy Dunlap
2006-10-02 6:32 ` Olaf Hering
2006-09-16 11:47 ` Arjan van de Ven
2006-09-17 0:48 ` rossb
2006-09-17 1:13 ` Adrian Bunk [this message]
2006-10-02 7:08 Mikael Pettersson
2006-10-02 10:42 ` Olivier Galibert
-- strict thread matches above, loose matches on Subject: below --
2006-10-02 11:23 Mikael Pettersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060917011352.GM669@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@google.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rossb@google.com \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox