From: Andrew Morton <akpm@digeo.com>
To: Dave McCracken <dmccr@us.ibm.com>
Cc: zilvinas@gemtek.lt, helgehaf@aitel.hist.no,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.62-mm3 - no X for me
Date: Tue, 25 Feb 2003 13:27:55 -0800 [thread overview]
Message-ID: <20030225132755.241e85ac.akpm@digeo.com> (raw)
In-Reply-To: <131360000.1046195828@[10.1.1.5]>
Dave McCracken <dmccr@us.ibm.com> wrote:
>
>
> --On Tuesday, February 25, 2003 01:55:37 -0800 Andrew Morton
> <akpm@digeo.com> wrote:
>
> > Ah, thank you.
> >
> > kernel BUG at mm/rmap.c:248!
> >
> > The fickle finger of fate points McCrackenwards.
>
> Yep. He tripped over my sanity check that pages not marked anon actually
> have a real mapping pointer. Apparently X allocates a page that should be
> marked anon but isn't.
Wonder where that came from?
> My main reason for adding the anon flag was to prove to myself that the
> mapping pointer can be trusted. Apparently it can, generally, but it looks
> like I haven't successfully tracked down all the places that should set it.
> It looks like anon pages can come from random sources, so it might be an
> impossible task to find them all.
Yes, the debug check is important at this time.
> I know you said you like the idea of having the flag, but I think the
> cleanest fix would be to change the check from
>
> if (PageAnon(page))
> to
> if (page->mapping && !PageSwapCache(page))
Well I'm not particularly overjoyed by the flag. What I liked was that we
have a place where we can implement anonymous page counting, so we get
another interesting number in /proc/meminfo. Minor point.
> Or I could set the anon flag based on that test. I know page flags are
> getting scarce, so I'm leaning toward removing the flag entirely.
>
> What would you recommend?
Keep the flag for now, find the escaped page under X, remove the flag later?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-02-25 21:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 7:00 2.5.62-mm3 Andrew Morton
2003-02-24 12:26 ` 2.5.62-mm3 - no X for me Helge Hafting
2003-02-24 20:16 ` Andrew Morton
2003-02-25 9:45 ` Zilvinas Valinskas
2003-02-25 9:55 ` Andrew Morton
2003-02-25 17:57 ` Dave McCracken
2003-02-25 21:27 ` Andrew Morton [this message]
2003-02-25 21:46 ` Dave McCracken
2003-02-25 23:02 ` [PATCH 2.5.62-mm3] objrmap fix for X Dave McCracken
2003-02-26 6:14 ` Martin J. Bligh
2003-02-26 17:52 ` Martin J. Bligh
2003-02-26 18:03 ` Marc-Christian Petersen
2003-02-26 18:24 ` Martin J. Bligh
2003-03-01 9:31 ` Anton Blanchard
2003-02-25 18:49 ` 2.5.62-mm3 -Panics during dbt2 run Cliff White
2003-02-25 19:12 ` Andrew Morton
2003-02-25 22:37 ` 2.5.62-mm3 -DBT2 (was) " Cliff White
2003-02-24 18:04 ` 2.5.62-mm3 won't mount root Steven Cole
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=20030225132755.241e85ac.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=dmccr@us.ibm.com \
--cc=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=zilvinas@gemtek.lt \
/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