From: Benjamin Herrenschmidt <bh40@calva.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Paul Mackerras <paulus@linuxcare.com>,
Linux -Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: success 2.4.0-test8 with latest bk
Date: Wed, 13 Sep 2000 14:45:16 +0200 [thread overview]
Message-ID: <20000913124516.15351@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10009130011300.372-100000@cassiopeia.home>
>Usually this means that some function/data is marked __init while it
must not.
>Quick verification: #undef __init / #define __init etc.
>
>Just wondering: wouldn't it be possible to write some tool to find such bugs?
Yup, we could probably, instead of freeing the __init section, mark it
unaccessible with the MMU. This would put us in xmon as soon as we try to
access one of these. I'm not sure if this can be done without disabling
the BAT mapping of the kernel, however. Well, of course, that would be a
DEBUG option, not a feature of the "standard" kernel.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-13 12:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-12 20:49 success 2.4.0-test8 with latest bk Andreas Tobler
2000-09-12 21:11 ` Martin Costabel
2000-09-12 22:14 ` Geert Uytterhoeven
2000-09-13 12:45 ` Benjamin Herrenschmidt [this message]
2000-09-13 12:46 ` Martin Costabel
2000-09-13 12:47 ` Benjamin Herrenschmidt
2000-09-13 12:58 ` Michel Dänzer
2000-09-13 20:25 ` Michel Lanners
2000-09-13 21:20 ` Martin Costabel
2000-09-14 1:13 ` Takashi Oe
2000-09-14 3:38 ` Paul Mackerras
2000-09-14 6:50 ` Takashi Oe
2000-09-17 5:32 ` Troy Benjegerdes
-- strict thread matches above, loose matches on Subject: below --
2000-09-13 15:56 Iain Sandoe
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=20000913124516.15351@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com \
/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).