public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: module compiler version check still needed?
Date: Mon, 14 Aug 2006 11:19:46 +0200	[thread overview]
Message-ID: <200608141119.46259.ak@suse.de> (raw)
In-Reply-To: <1155546377.2886.190.camel@laptopd505.fenrus.org>

On Monday 14 August 2006 11:06, Arjan van de Ven wrote:
> On Sun, 2006-08-13 at 06:48 +0200, Andi Kleen wrote:
> > Does anybody know of any reason why we would still need the compiler version
> > check during module loading? AFAIK on i386 it was only needed to handle
> > 2.95 (which got dropped) and on x86-64 it was never needed. Is there
> > a need on any other architecture for it?
> 
> is there any harm in doing this check?

Yes, it can cause lots of trouble when you try to compile external
modules on a different system with different compiler than on the
system where the kernel was compiled.

e.g. you upgrade a distribution kernel but now you can compile
modules for it because the new rpm was compiled with a newer 
compiler.

Happens to me regularly.

-Andi

  reply	other threads:[~2006-08-14  9:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-13  4:48 module compiler version check still needed? Andi Kleen
2006-08-13  4:59 ` Keith Owens
2006-08-13 20:27   ` Andi Kleen
2006-08-13 22:04     ` Adrian Bunk
2006-08-13 22:14     ` Matthew Wilcox
2006-08-14  4:59       ` Andi Kleen
2006-08-14  5:38         ` Sam Ravnborg
2006-08-14  5:45           ` Andi Kleen
2006-08-14  9:06 ` Arjan van de Ven
2006-08-14  9:19   ` Andi Kleen [this message]
2006-08-14 22:11     ` Adrian Bunk

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=200608141119.46259.ak@suse.de \
    --to=ak@suse.de \
    --cc=arjan@infradead.org \
    --cc=linux-arch@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox