public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: kasten@nscl.msu.edu
Cc: linux-kernel@vger.kernel.org, "Ken Sandars" <ksandars@eurologic.com>
Subject: Re: BUG: v2.4.1 missing EXPORT_SYMBOL
Date: Thu, 01 Feb 2001 11:40:32 +1100	[thread overview]
Message-ID: <9869.980988032@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 31 Jan 2001 15:44:29 CDT." <200101312044.PAA11405@tiger.nscl.msu.edu>

On Wed, 31 Jan 2001 15:44:29 -0500 (EST), 
Eric Kasten <kasten@nscl.msu.edu> wrote:
>Quick bug report for kernel 2.4.1.  There needs to be a
>EXPORT_SYMBOL(name_to_kdev_t); at the bottom of linux/init/main.c.
>name_to_kdev_t is used by the md driver (and maybe others).  If the
>driver is built as a module it won't load due to the missing symbol.

Don't blame us when the driver gets an oops.  name_to_kdev_t is defined
__init so the code is discarded after boot and the area is reused as
scratch space.  You must not EXPORT_SYMBOL() any __init or __exit code.

The only place name_to_kdev_t is used in md is in the md_setup routine,
that routine probably only makes sense when md is built in, not when md
is a module.  I recommend wrapping md_setup and all its data in #ifndef
MODULE.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-02-01  0:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-31 20:44 BUG: v2.4.1 missing EXPORT_SYMBOL Eric Kasten
2001-01-31 21:04 ` Ken Sandars
2001-02-01  0:40 ` Keith Owens [this message]
2001-02-01 15:15   ` BUG: " Eric Kasten

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=9869.980988032@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=kasten@nscl.msu.edu \
    --cc=ksandars@eurologic.com \
    --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