From: Andi Kleen <ak@suse.de>
To: Arjan van de Ven <arjan@infradead.org>
Subject: Re: module compiler version check still needed?
Date: Mon, 14 Aug 2006 11:19:46 +0200
User-Agent: KMail/1.9.3
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
References: <200608130648.36178.ak@suse.de> <1155546377.2886.190.camel@laptopd505.fenrus.org>
In-Reply-To: <1155546377.2886.190.camel@laptopd505.fenrus.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200608141119.46259.ak@suse.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1015
Lines: 25

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/