mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Olivier Galibert <galibert@pobox.com>
To: linux-kernel@vger.kernel.org
Subject: Re: + allow-proc-configgz-to-be-built-as-a-module.patch added to -mm tree
Date: Sat, 16 Sep 2006 02:23:27 +0200	[thread overview]
Message-ID: <20060916002326.GA69619@dspnet.fr.eu.org> (raw)
In-Reply-To: <20060915164135.34adb303.akpm@osdl.org>

On Fri, Sep 15, 2006 at 04:41:35PM -0700, Andrew Morton wrote:
> I'd want to be hearing from distro people on that - I'd expect that the
> .config which is used to build configs.ko would not differ from that which
> is used to build vmlinux.

What's the point though?  If you can find configs.ko, you can have
install_modules copy config.gz there, no?  And you also have it in
/boot/config-`uname -r`.  /proc/config.gz has a trust value only
because it is linked into the image.  Having it as a module gives the
exact save level of trustyness that the perfectly well working
solution of copying in /boot had before.

In other terms, if you allow configs.ko, you can't trust the contents
of /proc/config.gz anymore and /proc/config.gz lost all its interest
where it comes to debugging.

  OG.


  parent reply	other threads:[~2006-09-16  0:23 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 ` 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 [this message]
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
2006-10-02  7:08 Mikael Pettersson
2006-10-02 10:42 ` Olivier Galibert
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=20060916002326.GA69619@dspnet.fr.eu.org \
    --to=galibert@pobox.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®