mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: kernel-janitors@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: reference_init.pl for Linux 2.6
Date: Thu, 19 Feb 2004 09:35:27 -0800	[thread overview]
Message-ID: <20040219093527.77b7b053.rddunlap@osdl.org> (raw)
In-Reply-To: <2263.1077192048@ocs3.ocs.com.au>

On Thu, 19 Feb 2004 23:00:48 +1100 Keith Owens <kaos@ocs.com.au> wrote:

| On Wed, 18 Feb 2004 18:23:13 -0800, 
| "Randy.Dunlap" <rddunlap@osdl.org> wrote:
| >I have updated Keith Owens "reference_init.pl" script for
| >Linux 2.6.  It searches for code that refers to other code
| >sections that they should not reference, such as init code
| >calling exit code or v.v.
| >script for Linux 2.6 is at:
| >http://developer.osdl.org/rddunlap/scripts/reference_init26.pl
| 
| You added '$from !~ /\.data/'.  Any references from the .data section
| to .init or .exit text should be checked.  It is usually a struct
| containing a pointer to code that will be discarded, and is dangerous.
| 
| There is also a spurious comment line,
| #                   $from !~ $line && $line !~ $from &&
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Both fixed and reposted.
The output probably has a bit more false positives reported now.

script:
http://developer.osdl.org/rddunlap/scripts/reference_init26.pl

output on linux-2.6.3 with CONFIG_HOTPLUG=n and very few modules:
http://developer.osdl.org/rddunlap/scripts/badrefs.out


Thanks, Keith.
--
~Randy

  reply	other threads:[~2004-02-19 17:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19  2:23 Randy.Dunlap
2004-02-19  2:51 ` Dave Jones
2004-02-19 12:00 ` Keith Owens
2004-02-19 17:35   ` Randy.Dunlap [this message]
2004-02-19 18:31 Rui Saraiva

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=20040219093527.77b7b053.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=kaos@ocs.com.au \
    --cc=kernel-janitors@osdl.org \
    --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

all inboxes | Powered by JetHome®