From: Robert Hancock <hancockrwd@gmail.com>
To: Carmelo Amoroso <carmelo73@gmail.com>
Cc: Greg KH <greg@kroah.com>,
Alan Jenkins <sourcejedi.lkml@googlemail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: Fast LKM symbol resolution with SysV ELH hash table
Date: Tue, 20 Oct 2009 23:43:44 -0600 [thread overview]
Message-ID: <4ADE9F90.8060608@gmail.com> (raw)
In-Reply-To: <2ccd6e3c0910190802w117f8ac1nb562214786904c04@mail.gmail.com>
On 10/19/2009 09:02 AM, Carmelo Amoroso wrote:
> 2009/10/19 Greg KH<greg@kroah.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..
next prev parent reply other threads:[~2009-10-21 5:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-18 8:09 Fast LKM symbol resolution with SysV ELH hash table Carmelo Amoroso
2009-10-18 12:44 ` Alan Jenkins
2009-10-18 16:43 ` Alan Jenkins
2009-10-18 21:47 ` Greg KH
2009-10-19 0:01 ` Alan Jenkins
2009-10-19 11:45 ` Carmelo Amoroso
2009-10-19 13:22 ` Greg KH
2009-10-19 15:02 ` Carmelo Amoroso
2009-10-19 19:10 ` Greg KH
2009-10-19 20:46 ` Alan Jenkins
2009-10-20 0:56 ` Rusty Russell
2009-10-21 5:43 ` Robert Hancock [this message]
2009-10-21 13:48 ` Greg KH
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=4ADE9F90.8060608@gmail.com \
--to=hancockrwd@gmail.com \
--cc=carmelo73@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sourcejedi.lkml@googlemail.com \
/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