linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: Sean Hunter <sean@dev.sportingbet.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RFC: modules and 2.5
Date: Tue, 03 Jul 2001 03:44:36 -0400	[thread overview]
Message-ID: <3B4177E4.CEFB99FB@mandrakesoft.com> (raw)
In-Reply-To: <2422.994145942@kao2.melbourne.sgi.com>

Keith Owens wrote:
> Human error.  Create a new kernel with something built in which used to
> be a module and forget to make modules_install, so the code is in the
> kernel and in /lib/modules.  Then do an explicit insmod, if probing
> does not fail the module load then oops is all she wrote.

It still sounds like a driver bug.  It is the driver's responsibility to
ensure its resources are locked down for its own use.

Probing should not succeed if there is an existing driver in the
kernel.  request_??? and register_??? functions return failure to
guarantee this sort of thing.

Someone please provide a list of drivers which behave in this manner, so
that they can be fixed up.

Regards,

	Jeff


-- 
Jeff Garzik      | "I respect faith, but doubt is
Building 1024    |  what gives you an education."
MandrakeSoft     |           -- Wilson Mizner

  reply	other threads:[~2001-07-03  7:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-03  5:13 RFC: modules and 2.5 Jeff Garzik
2001-07-03  6:50 ` Sean Hunter
2001-07-03  7:05   ` Jeff Garzik
2001-07-03  7:16   ` Keith Owens
2001-07-03  7:24     ` Jeff Garzik
2001-07-03  7:39       ` Keith Owens
2001-07-03  7:44         ` Jeff Garzik [this message]
2001-07-03  7:48   ` Fang Han
2001-07-03  7:18 ` Keith Owens
2001-07-03 12:15 ` jlnance
2001-07-06 10:34 ` Rusty Russell
2001-07-07 14:12   ` Jeff Garzik
2001-07-08  7:40     ` Rusty Russell
2001-07-11 22:04       ` Pavel Machek
2001-07-03 17:35 Andrzej Krzysztofowicz
2001-07-03 17:39 ` Jeff Garzik

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=3B4177E4.CEFB99FB@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sean@dev.sportingbet.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;
as well as URLs for NNTP newsgroup(s).