From: Matthias Andree <matthias.andree@gmx.de>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Andrew Morton <akpm@osdl.org>,
matthias.andree@gmx.de, andrea@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.25 SMP - BUG at page_alloc.c:105
Date: Wed, 24 Mar 2004 22:36:48 +0100 [thread overview]
Message-ID: <20040324213648.GA17896@merlin.emma.line.org> (raw)
In-Reply-To: <20040324215112.GA6931@logos.cnet>
On Wed, 24 Mar 2004, Marcelo Tosatti wrote:
> This should work. Matthias, please apply and try to reproduce.
Didn't compile. I have changed that line 119 to bad_page(__FUNCTION__,
page); instead. If the first argument must be something else, let me
know. It doesn't immedately make sense with just one caller, but I know
nothing better right now.
As I don't know a specific scenario to reproduce the crash, it may take
longer (possibly weeks) until I can come up with results.
Here's the error:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.25/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon -nostdinc -iwithprefix include -DKBUILD_BASENAME=page_alloc -DEXPORT_SYMTAB -c page_alloc.c
page_alloc.c: In function `__free_pages_ok':
page_alloc.c:119: warning: passing arg 1 of `bad_page' from incompatible pointer type
page_alloc.c:119: error: too few arguments to function `bad_page'
make[2]: *** [page_alloc.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.4.25/mm'
The relevant parts of the patch were:
> --- mm/page_alloc.c.orig 2004-03-24 18:42:53.693251224 -0300
> +++ mm/page_alloc.c 2004-03-24 18:47:52.484828000 -0300
> @@ -81,6 +81,20 @@
> * -- wli
> */
>
> +static void bad_page(const char *function, struct page *page)
> +{
> + printk("Bad page state at %s\n", function);
...
> @@ -101,8 +115,8 @@
>
> if (page->buffers)
> BUG();
> - if (page->mapping)
> - BUG();
> + if (page->mapping)
> + bad_page(page);
> if (!VALID_PAGE(page))
> BUG();
> if (PageLocked(page))
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
next prev parent reply other threads:[~2004-03-24 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 20:58 Marcelo Tosatti
2004-03-24 20:28 ` Andrew Morton
2004-03-24 21:12 ` Matthias Andree
2004-03-24 21:51 ` Marcelo Tosatti
2004-03-24 21:36 ` Matthias Andree [this message]
2004-03-25 0:22 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2004-03-22 14:49 Matthias Andree
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=20040324213648.GA17896@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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
all inboxes | Powered by JetHome®