From: Benjamin Herrenschmidt <bh40@calva.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: free_initmem() bug
Date: Thu, 3 Aug 2000 15:28:13 +0200 [thread overview]
Message-ID: <20000803132813.29461@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10007311937060.442-100000@cassiopeia.home>
>
>free_initmem() must not be __init because that means sawing the branch
>underneat itselves, which may cause a crash.
>
>I also optimized the freeing of the various sections, both from a soure and
>object view.
>
>The patch is half tested, i.e. it compiles. Since I won't be able to do
bk for
>a while, can someone please take care of this? Thanks!
Ah, this might explain some problems I had with 2.4 hangs on freeing init
mem...
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-08-03 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-02 20:11 free_initmem() bug Geert Uytterhoeven
2000-08-03 13:28 ` Benjamin Herrenschmidt [this message]
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=20000803132813.29461@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.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).