All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Sigler <linux.kernel@free.fr>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dumping the checksums in a module
Date: Tue, 19 Jun 2007 16:40:15 +0200	[thread overview]
Message-ID: <4677EACF.2000202@free.fr> (raw)
In-Reply-To: <1182259085.3014.5.camel@laptopd505.fenrus.org>

Arjan van de Ven wrote:

> On Tue, 2007-06-19 at 13:59 +0200, John Sigler wrote:
>
>> As far as I understand (which is not very far), if I define
>> CONFIG_MODVERSIONS,
> 
> just don't enable modversions.. it doesn't provide you any real safety
> at all..... and it makes your build a LOT slower.

I'm confused. What is the consensus on MODVERSIONS around here?
How many people share your views?

I was under the impression MODVERSIONS was a good thing(TM).

If I don't enable CONFIG_MODVERSIONS, then I'll have to recompile my 
out-of-tree modules every time I upgrade the kernel, even if I'm just 
upgrading from 2.6.20.7 to 2.6.20.8, unless I force the insertion.

I also have a few binary modules. If I force the insertion, I won't know 
they have become binary incompatible until they blow up later, or, 
worse, lead to silent corruption.

Please correct any and all misconceptions.

Regards.

  reply	other threads:[~2007-06-19 14:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 11:59 Dumping the checksums in a module John Sigler
2007-06-19 13:18 ` Arjan van de Ven
2007-06-19 14:40   ` John Sigler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-18 15:02 John Sigler
2007-05-18 20:27 ` Jan Engelhardt
2007-05-18 20:46   ` Sam Ravnborg
2007-05-22  8:19     ` John Sigler
2007-05-22  8:13   ` John Sigler
2007-05-22 19:53     ` Jan Engelhardt
2007-05-23 15:18       ` John Sigler

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=4677EACF.2000202@free.fr \
    --to=linux.kernel@free.fr \
    --cc=arjan@infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.