From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Marcin Ro?ek <marcin.rozek@ios.edu.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at page_alloc.c
Date: Wed, 15 Sep 2004 09:44:50 -0300 [thread overview]
Message-ID: <20040915124449.GB2963@logos.cnet> (raw)
In-Reply-To: <414844C5.6080802@ios.edu.pl>
On Wed, Sep 15, 2004 at 03:33:57PM +0200, Marcin Ro?ek wrote:
> Marcelo Tosatti wrote:
> >Its the third or fourth report like this I see, all of them with the
> >grsecurity patch applied.
> >
> >Have you tried a stock 2.4.27?
> No.
> Is that bug serious? Should i move to clean 2.4.27?
Yes it is quite serious... the VM is trying to free a page with ->mapping
set (probably a pagecache page) which is not valid thing to happen (thus the BUG).
You can move to v2.4.27 to confirm you see or do not see the problem there.
> Strange is that previously i've been running (for quite long time) Mandrake
> 9.1 on the same machine with 2.4.27-grsec (but with enabled
> CONFIG_GRKERNSEC_PAX_MPROTECT) and i don't remember seeing such BUG...A
Search the archives for "grsecurity and 2.4.27" and take a look
at the other reports.
next prev parent reply other threads:[~2004-09-15 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 12:25 kernel BUG at page_alloc.c Marcin Rożek
2004-09-15 11:21 ` Marcelo Tosatti
2004-09-15 13:33 ` Marcin Rożek
2004-09-15 12:44 ` Marcelo Tosatti [this message]
2004-09-17 11:02 ` Marcin Rożek
[not found] <20020812002223.GE24456@louise.pinerecords.com>
2002-08-12 0:27 ` Studying MTD
2002-08-12 0:41 ` Studying MTD
2002-08-12 0:46 ` Tomas Szepe
[not found] <20020812000523.15F1D88BC@oscar.casa.dyndns.org>
2002-08-12 0:19 ` Studying MTD
-- strict thread matches above, loose matches on Subject: below --
2002-08-11 23:35 Studying MTD
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=20040915124449.GB2963@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.rozek@ios.edu.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.