From: Andrew Morton <akpm@osdl.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: rddunlap@osdl.org, geert@linux-m68k.org, davej@redhat.com,
torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: __init dependencies
Date: Mon, 11 Oct 2004 21:19:32 -0700 [thread overview]
Message-ID: <20041011211932.3fad6bf9.akpm@osdl.org> (raw)
In-Reply-To: <416B57DE.4070605@osdl.org>
"Randy.Dunlap" <rddunlap@osdl.org> wrote:
>
> My experience with output of buildcheck is that it's verbose and has
> lots of false positives.
I berated Keith over that a while back and he shot me down. umm...
> On Mon, 31 May 2004 23:52:14 -0700,
> Andrew Morton <akpm@osdl.org> wrote:
> >
> >gad, reference_init generates so much stuff I wonder if it's worth using.
> >Are all these for real?
>
> Apart from altinstructions, yes. Mainly because people have not been
> checking them.
>
> >perl scripts/reference_init.pl
> >Finding objects, 1411 objects, ignoring 122 module(s)
> >Finding conglomerates, ignoring 137 conglomerate(s)
> >Scanning objects
> >Error: ./arch/i386/kernel/apic.o .data refers to 0000009c R_386_32 .init.text
>
> arch/i386/kernel/apic.c
> void (*wait_timer_tick)(void) = wait_8254_wraparound;
> wait_8254_wraparound is __init. wait_timer_tick should be __initdata,
> which flows onto several other functions.
>
> >Error: ./arch/i386/kernel/cpu/mtrr/centaur.o .data refers to 00000008 R_386_32 .init.text
>
> That is real, centaur_mtrr_ops.init = centaur_mcr_init. Like a lot of
> this initialization code, we get away with the dangling reference
> because the code is only executed at boot.
>
> >Error: ./arch/i386/kernel/cpu/mtrr/centaur.o .eh_frame refers to 000000dc R_386_32 .init.text
>
> I don't see any .eh_frame references in 2.6.7-rc2 using gcc version
> 3.3.3 20040412 (Red Hat Linux 3.3.3-7). Where are they coming from?
>
> >Error: ./arch/i386/kernel/cpu/mtrr/cyrix.o .data refers to 00000028 R_386_32 .init.text
>
> Same as centaur.
>
> >Error: ./arch/i386/kernel/cpu/mtrr/generic.o .text refers to 0000038f R_386_32 .init.data
>
> arch/i386/kernel/cpu/mtrr/generic.c
> generic_set_all() uses __intdata smp_changes_mask.
>
> >Error: ./arch/i386/kernel/smpboot.o .altinstructions refers to 00000000 R_386_32 .init.text
>
> altinstructions is a false positive, tweak reference_init.pl
>
> --- reference_init.pl.orig 2004-06-01 20:30:27.000000000 +1000
> +++ reference_init.pl 2004-06-01 20:31:01.000000000 +1000
> @@ -93,6 +93,7 @@
> $from !~ /\.stab$/ &&
> $from !~ /\.rodata$/ &&
> $from !~ /\.text\.lock$/ &&
> + $from !~ /\.altinstructions$/ &&
> $from !~ /\.debug_/)) {
> printf("Error: %s %s refers to %s\n", $object, $from, $line);
> }
>
> The rest of the warnings look real, apart from the strange eh_frame.
>
So what you think are false positives may well not be.
next prev parent reply other threads:[~2004-10-12 4:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 22:57 [PATCH] find_isa_irq_pin can't be __init Dave Jones
2004-10-11 11:33 ` __init dependencies (was: Re: [PATCH] find_isa_irq_pin can't be )__init Geert Uytterhoeven
2004-10-11 19:12 ` Andrew Morton
2004-10-11 19:16 ` Dave Jones
2004-10-11 19:17 ` __init dependencies Randy.Dunlap
2004-10-12 4:04 ` Randy.Dunlap
2004-10-12 4:19 ` Andrew Morton [this message]
2004-10-12 6:06 ` Keith Owens
2004-10-20 16:08 ` [PATCH] __init dependencies: ignore __param Randy.Dunlap
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=20041011211932.3fad6bf9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=torvalds@osdl.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®