mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Goran Cengic <cengic@s2.chalmers.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Special place for tird-party modules.
Date: Wed, 28 Apr 2004 15:18:25 -0400	[thread overview]
Message-ID: <200404281918.i3SJIPPR005391@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 28 Apr 2004 18:14:24 +0200." <200404281814.24991.cengic@s2.chalmers.se>

[-- Attachment #1: Type: text/plain, Size: 996 bytes --]

On Wed, 28 Apr 2004 18:14:24 +0200, Goran Cengic <cengic@s2.chalmers.se>  said:

> I do understand that many developers have several kernel version installed at
> the same time but is it possible to share between the versions at least the 
> modules that are not developed as the part of the kernel?
> 
> If I'm missing something cruical please point it out to me.

What you're missing is the reason for modversions to exist - the fact that the
kernel API *does* change between releases, and even within the same source tree
(UP vs SMP builds, for instance).  If we supported what you're suggesting, then
the following *will* happen:

1) Binary module for 2.6.N is released that uses an API that takes 5 parameters.
2) 2.6.N+1 comes out, and said API has another parameter added (see the recent
tweak-fest for elf_map() for an actual example).
3) User loads old binary into kernel.
4) Kernel OOPs when it dereferences the non-existent 6th parameter that wasn't
passed by the un-updated binary.



[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  parent reply	other threads:[~2004-04-28 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-28 16:14 Goran Cengic
     [not found] ` <200404281835.24836.bzolnier@elka.pw.edu.pl>
2004-04-28 17:05   ` Goran Cengic
2004-04-28 21:18     ` Valdis.Kletnieks
2004-04-28 19:18 ` Valdis.Kletnieks [this message]
2004-04-29  8:15   ` Goran Cengic

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=200404281918.i3SJIPPR005391@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=cengic@s2.chalmers.se \
    --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

all inboxes | Powered by JetHome®