From: Balbir Singh <balbir@in.ibm.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrea Arcangeli <andrea@suse.de>,
Petr Tesarik <ptesarik@suse.cz>, Hugh Dickins <hugh@veritas.com>
Subject: Re: [rfc][patch] rmap: more sanity checks
Date: Wed, 14 Feb 2007 22:22:25 +0530 [thread overview]
Message-ID: <45D33E49.8070909@in.ibm.com> (raw)
In-Reply-To: <20070214090425.GA14932@wotan.suse.de>
Nick Piggin wrote:
> We have seen a bug in SLES9 that only gets picked up with Andrea's extra
> rmap checks that were removed from mainline.
>
> Petr Tesarik has got a fix for the problem, which he is planning to send
> upstream. The issue is a specific condition that causes an anon page to be
> incorrectly inserted into the pagetables, outside a valid vma.
>
> It would be nice to get some of these checks back into mainline, IMO. I
> wonder if I'm correct in thinking that checking the page index and mapping
> is not actually racy?
>
I hope so, if that is indeed the case my patches for tracking and accounting
shared rss pages at
http://marc.theaimsgroup.com/?l=linux-mm&m=116738715329816&w=2
will get much simpler.
There used to be a rmap lock (PG_maplock bit) earlier to protect
rmap information
Please see
http://marc.theaimsgroup.com/?l=linux-mm&m=116738715302690&w=2
and
http://lkml.org/lkml/2004/7/12/241
Regards,
Balbir Singh
--
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:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2007-02-14 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 9:04 [rfc][patch] rmap: more sanity checks Nick Piggin
2007-02-14 16:50 ` Andrea Arcangeli
2007-02-15 0:46 ` Nick Piggin
2007-02-14 16:52 ` Balbir Singh [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=45D33E49.8070909@in.ibm.com \
--to=balbir@in.ibm.com \
--cc=andrea@suse.de \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=ptesarik@suse.cz \
/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).