[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ADE9F90.8060608@gmail.com>
Date: Tue, 20 Oct 2009 23:43:44 -0600
From: Robert Hancock <hancockrwd@...il.com>
To: Carmelo Amoroso <carmelo73@...il.com>
CC: Greg KH <greg@...ah.com>,
Alan Jenkins <sourcejedi.lkml@...glemail.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Rusty Russell <rusty@...tcorp.com.au>,
linux-kbuild <linux-kbuild@...r.kernel.org>
Subject: Re: Fast LKM symbol resolution with SysV ELH hash table
On 10/19/2009 09:02 AM, Carmelo Amoroso wrote:
> 2009/10/19 Greg KH<greg@...ah.com>:
>> On Mon, Oct 19, 2009 at 01:45:20PM +0200, Carmelo Amoroso wrote:
>>> Just a few other notes. The current implementation I did based on SysV
>>> has a drawback that is not backward compatible, so you cannot use old
>>> modules with a kernel with the option enabled due to changes on struct
>>> kernel_symbol.
>>
>> Why would this be a problem? Whenever making a kernel config change,
>> you should be able to rebuild everything, as lots of other configuration
>> options are that way.
>>
>
> This is not always true... there could be cases in which you cannot
> recompile old modules
> (e.g vendors that provide non GPL modules)
Even non-GPL modules can normally be rebuilt as far as the module format
is concerned, there's usually an object file blob that gets compiled
into a module on install or something, like the Nvidia graphics driver.
If anyone's providing binary-only fully built modules (which would be
inherently tied to one exact kernel version and one configuration) they
really need to have their head examined..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists