mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Masters <jonathan@jonmasters.org>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Valdis.Kletnieks@vt.edu, "Frank Ch. Eigler" <fche@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Christoph Hellwig <hch@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] Linux Kernel Markers Support for Proprierary Modules
Date: Thu, 24 Jan 2008 15:35:31 -0500	[thread overview]
Message-ID: <1201206932.25284.143.camel@perihelion> (raw)
In-Reply-To: <20080124124703.GB32559@Krystal>


On Thu, 2008-01-24 at 07:47 -0500, Mathieu Desnoyers wrote:
> There seems to be good arguments for markers to support proprierary modules. So
> I am throwing this one-liner in and let's see how people react. It only makes
> sure that a module that has been "forced" to be loaded won't have its markers
> used. It is important to leave this check to make sure the kernel does not crash
> by expecting the markers part of the struct module by mistake in the case there
> is an incorrect checksum.
> 
> It applies fine on 2.6.24-rc8-git3.

I think this should go in.

Signed-off-by: Jon Masters <jcm@jonmasters.org>

Jon.

P.S. wondering out loud to myself, I finally realized the reason we need
a leaf struct_module function in kernel/module.c. We don't necessarily
have anything else checking for changes to struct module on module load
without this, and we have an embedded struct module in each module that
we memory map as we load the module. I did wonder what was protecting us
from that (especially forced loads). But Rusty does think of everything.



  parent reply	other threads:[~2008-01-24 20:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 19:13 CONFIG_MARKERS Jon Masters
2008-01-23  3:00 ` CONFIG_MARKERS Frank Ch. Eigler
2008-01-23  3:10   ` CONFIG_MARKERS Mathieu Desnoyers
2008-01-23  4:17     ` CONFIG_MARKERS Jon Masters
2008-01-23 13:14       ` CONFIG_MARKERS Frank Ch. Eigler
2008-01-23 14:48         ` CONFIG_MARKERS Mathieu Desnoyers
2008-01-23 15:01           ` CONFIG_MARKERS Mathieu Desnoyers
2008-01-23 16:33             ` CONFIG_MARKERS Jon Masters
2008-01-23 17:11               ` CONFIG_MARKERS Mathieu Desnoyers
2008-01-24  5:25           ` CONFIG_MARKERS Valdis.Kletnieks
2008-01-24  6:19             ` CONFIG_MARKERS Jon Masters
2008-01-24 12:47               ` [PATCH] Linux Kernel Markers Support for Proprierary Modules Mathieu Desnoyers
2008-01-24 18:27                 ` Valdis.Kletnieks
2008-01-24 20:35                 ` Jon Masters [this message]
2008-01-25  1:27                 ` Rusty Russell
2008-01-25  7:56                 ` Jan Engelhardt
2008-01-25  8:03                   ` Valdis.Kletnieks
2008-01-25 16:32                     ` Alan Cox
2008-01-25 15:31                   ` Jon Masters
2008-01-25 16:01                     ` Jan Engelhardt
2008-01-26  3:27                     ` Rusty Russell
2008-01-26  4:21                       ` Jon Masters
2008-01-27 10:48                         ` Jan Engelhardt
2008-02-02 19:51 Mathieu Desnoyers

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=1201206932.25284.143.camel@perihelion \
    --to=jonathan@jonmasters.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=fche@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@linux-foundation.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®