public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org, trini@kernel.crashing.org
Subject: Re: [PATCH] PREEMPT_RT vermagic
Date: Wed, 31 Aug 2005 09:20:17 +0200	[thread overview]
Message-ID: <20050831072017.GA7125@elte.hu> (raw)
In-Reply-To: <1125441737.18150.43.camel@dhcp153.mvista.com>


* Daniel Walker <dwalker@mvista.com> wrote:

> Ingo,
> 	This patch adds a vermagic hook so PREEMPT_RT modules can be
> distinguished from PREEMPT_DESKTOP modules.

vermagic is very crude and there are zillions of other details and 
.config flags that might make a module incompatible. You can use 
CONFIG_MODVERSIONS to get a stronger protection that vermagic, but 
that's far from perfect too. The right solution is the module signing 
framework in Fedora. Until that gets merged upstream just dont mix 
incompatible modules, and keep things tightly packaged.

	Ingo

  reply	other threads:[~2005-08-31  7:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-29  8:48 2.6.13-rt1 Ingo Molnar
2005-08-29 11:09 ` 2.6.13-rt1 Steven Rostedt
2005-08-29 11:18   ` 2.6.13-rt1 Ingo Molnar
2005-08-29 15:04 ` 2.6.13-rt1 Daniel Walker
2005-08-29 15:18   ` 2.6.13-rt1 Ingo Molnar
2005-08-29 15:19     ` 2.6.13-rt1 Daniel Walker
2005-08-30  3:33 ` 2.6.13-rt1 Steven Rostedt
2005-08-30  5:53   ` 2.6.13-rt1 Ingo Molnar
2005-08-30 13:06     ` 2.6.13-rt1 Steven Rostedt
2005-08-30 22:34       ` 2.6.13-rt1 Daniel Walker
2005-08-31  1:10         ` 2.6.13-rt1 Steven Rostedt
2005-08-30 22:42 ` [PATCH] PREEMPT_RT vermagic Daniel Walker
2005-08-31  7:20   ` Ingo Molnar [this message]
2005-08-31 14:29     ` Tom Rini
2005-08-31 15:19       ` Tom Rini

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=20050831072017.GA7125@elte.hu \
    --to=mingo@elte.hu \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.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