From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Gerd Hoffman <kraxel@suse.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.16-rc1-mm4
Date: Tue, 31 Jan 2006 21:44:20 -0500 [thread overview]
Message-ID: <200601312146_MC3-1-B74E-D5C4@compuserve.com> (raw)
In-Reply-To: <20060129144533.128af741.akpm@osdl.org>
$ perl scripts/reference_init.pl | grep smp_locks
Error: ./arch/i386/kernel/alternative.o .smp_locks refers to 00000008 R_386_32 .init.text
Error: ./arch/i386/kernel/apic.o .smp_locks refers to 00000000 R_386_32 .init.text
Error: ./arch/i386/kernel/apic.o .smp_locks refers to 00000010 R_386_32 .init.text
Error: ./arch/i386/kernel/apic.o .smp_locks refers to 00000014 R_386_32 .init.text
Error: ./arch/i386/kernel/cpu/amd.o .smp_locks refers to 00000000 R_386_32 .init.text
Error: ./arch/i386/kernel/cpu/amd.o .smp_locks refers to 00000004 R_386_32 .init.text
Error: ./arch/i386/kernel/cpu/amd.o .smp_locks refers to 00000008 R_386_32 .init.text
Error: ./arch/i386/kernel/cpu/amd.o .smp_locks refers to 0000000c R_386_32 .init.text
Error: ./arch/i386/kernel/cpu/amd.o .smp_locks refers to 00000010 R_386_32 .init.text
Error: ./arch/i386/kernel/cpu/amd.o .smp_locks refers to 00000014 R_386_32 .init.text
Error: ./arch/i386/kernel/cpu/amd.o .smp_locks refers to 00000018 R_386_32 .init.text
Error: ./arch/i386/kernel/cpu/centaur.o .smp_locks refers to 00000000 R_386_32 .init.text
Error: ./arch/i386/kernel/cpu/centaur.o .smp_locks refers to 00000004 R_386_32 .init.text
...
Caused by x86_smp_alternatives.patch
Does this mean that the SMP lock-switching could write all over discarded
__init code?
--
Chuck
next reply other threads:[~2006-02-01 2:47 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 2:44 Chuck Ebbert [this message]
2006-02-01 23:56 ` 2.6.16-rc1-mm4 Keith Owens
2006-02-02 8:58 ` 2.6.16-rc1-mm4 Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2006-02-01 4:28 2.6.16-rc1-mm4 Chuck Ebbert
2006-01-30 12:38 2.6.16-rc1-mm4 Gabriel C.
2006-01-29 22:45 2.6.16-rc1-mm4 Andrew Morton
2006-01-29 23:19 ` 2.6.16-rc1-mm4 Jesper Juhl
2006-01-29 23:34 ` 2.6.16-rc1-mm4 Adrian Bunk
2006-01-29 23:40 ` 2.6.16-rc1-mm4 Randy.Dunlap
2006-01-29 23:58 ` 2.6.16-rc1-mm4 Adrian Bunk
2006-01-30 0:51 ` 2.6.16-rc1-mm4 Randy.Dunlap
2006-01-30 0:59 ` 2.6.16-rc1-mm4 Adrian Bunk
2006-01-29 23:42 ` 2.6.16-rc1-mm4 Adrian Bunk
2006-01-30 0:25 ` 2.6.16-rc1-mm4 Andrew Morton
2006-01-30 0:42 ` 2.6.16-rc1-mm4 Eric W. Biederman
2006-01-29 23:43 ` 2.6.16-rc1-mm4 Brice Goglin
2006-01-30 9:40 ` 2.6.16-rc1-mm4 Muli Ben-Yehuda
2006-01-30 13:52 ` 2.6.16-rc1-mm4 Mark Maule
2006-01-30 13:59 ` 2.6.16-rc1-mm4 Muli Ben-Yehuda
2006-01-30 11:23 ` 2.6.16-rc1-mm4 Marc Koschewski
2006-01-30 11:31 ` 2.6.16-rc1-mm4 Andrew Morton
2006-01-30 13:20 ` 2.6.16-rc1-mm4 Al Boldi
2006-01-30 21:00 ` 2.6.16-rc1-mm4 Andrew Morton
2006-01-31 15:56 ` 2.6.16-rc1-mm4 Al Boldi
2006-01-31 22:01 ` 2.6.16-rc1-mm4 Andrew Morton
2006-02-01 0:50 ` 2.6.16-rc1-mm4 Randy.Dunlap
2006-02-01 13:58 ` 2.6.16-rc1-mm4 Al Boldi
2006-01-30 18:50 ` 2.6.16-rc1-mm4 Jindrich Makovicka
2006-01-30 19:04 ` 2.6.16-rc1-mm4 Martin Bligh
[not found] ` <3aa654a40601311445t65fc9b6aqf2d565b72ded9c1a@mail.gmail.com>
2006-01-31 23:10 ` 2.6.16-rc1-mm4 Andrew Morton
[not found] ` <3aa654a40602010154r54e0072bp3e7bd46ce9aafa03@mail.gmail.com>
2006-02-01 10:06 ` 2.6.16-rc1-mm4 Andrew Morton
2006-02-01 0:19 ` 2.6.16-rc1-mm4 Dave Jones
2006-02-01 0:59 ` 2.6.16-rc1-mm4 Dave Jones
2006-02-01 2:23 ` 2.6.16-rc1-mm4 Yasunori Goto
2006-02-01 2:30 ` 2.6.16-rc1-mm4 Andrew Morton
2006-02-01 4:38 ` 2.6.16-rc1-mm4 Kurt Wall
2006-02-01 4:40 ` 2.6.16-rc1-mm4 Andrew Morton
2006-02-01 4:57 ` 2.6.16-rc1-mm4 Kurt Wall
2006-02-01 5:16 ` 2.6.16-rc1-mm4 Kurt Wall
2006-02-01 9:34 ` 2.6.16-rc1-mm4 Russell King
2006-02-01 9:53 ` 2.6.16-rc1-mm4 Andrew Morton
2006-02-02 22:28 ` 2.6.16-rc1-mm4 J.A. Magallon
2006-02-02 22:47 ` 2.6.16-rc1-mm4 Andrew Morton
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=200601312146_MC3-1-B74E-D5C4@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=kraxel@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).