public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Modutils 2.5 change, start running this command now
Date: 03 Oct 2001 00:48:50 -0400	[thread overview]
Message-ID: <1002084533.858.1.camel@phantasy> (raw)
In-Reply-To: <31135.1002083784@kao2.melbourne.sgi.com>
In-Reply-To: <31135.1002083784@kao2.melbourne.sgi.com>

On Wed, 2001-10-03 at 00:36, Keith Owens wrote:
> In current modutils, a module that does not export symbols and does not
> say EXPORT_NO_SYMBOLS defaults to exporting all symbols.  This is a
> hangover from kernel 2.0 and will be removed when modutils 2.5 appears,
> shortly after the kernel 2.5 branch is created.

This is an excellent move.

> Starting with modutils 2.5, modules must explicitly say what their
> intention is for symbols.  That will break a lot of existing modules.
> The command below lists the modules on your system that will be
> affected.  All code maintainers need to run this against their 2.4
> modules and do one of two things.  Either export the required symbols
> (remember to add the .o file to export-objs in the Makefile) or add
> EXPORT_NO_SYMBOLS; somewhere in the module (no change to Makefile).

Once 2.5 starts, I'll be happy to go over modules with this script and
fix up stuff that is unmaintained.

>  objdump -h `modprobe -l` | \
>  awk '/file format/{file = $1}/__ksymtab/{file = ""}/\.comment/ && file != "" {print file}'

-- 
Robert M. Love
rml at ufl.edu
rml at tech9.net


  reply	other threads:[~2001-10-03  4:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-03  4:36 Modutils 2.5 change, start running this command now Keith Owens
2001-10-03  4:48 ` Robert Love [this message]
2001-10-03  8:17 ` Russell King
2001-10-03 11:59   ` Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2001-10-11 11:45 Keith Owens
2001-10-12  6:34 ` Ingo Oeser
2001-10-12 10:04 ` Benjamin LaHaise
2001-10-12 11:37   ` Keith Owens
2001-10-12 12:14     ` David Woodhouse
2001-10-12 14:40       ` Keith Owens
2001-10-12 15:01       ` 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=1002084533.858.1.camel@phantasy \
    --to=rml@tech9.net \
    --cc=kaos@ocs.com.au \
    --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