linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
	Petr Tesarik <ptesarik@suse.cz>, Hugh Dickins <hugh@veritas.com>
Subject: Re: [rfc][patch] rmap: more sanity checks
Date: Thu, 15 Feb 2007 01:46:38 +0100	[thread overview]
Message-ID: <20070215004638.GF29797@wotan.suse.de> (raw)
In-Reply-To: <20070214165047.GB11002@v2.random>

On Wed, Feb 14, 2007 at 05:50:47PM +0100, Andrea Arcangeli wrote:
> Hi Nick,
> 
> On Wed, Feb 14, 2007 at 10:04:25AM +0100, Nick Piggin wrote:
> > It would be nice to get some of these checks back into mainline, IMO. I
> 
> Obviously seconded. It's a bit ironic that my original implementation
> was effectively safer that what was further "sanitized" and pushed
> into mainline 8). (of course mainline over the dozen releases was
> significantly improved in the locking etc.etc.. I don't mean that, but
> as far as safety goes it clearly still lacks)

Yeah it is suboptimal to have mainline and possibly some other distros
missing out and getting silent corruption.

> This isn't the first time that we catch subtle VM bugs in sles9 that
> aren't reproducible in mainline (but that affects mainline too). I
> tried a few times to complain about the removal of my bugchecks
> (notably I recall the ones in do_no_page):
> 
> #ifndef CONFIG_DISCONTIGMEM
> 	/* this check is unreliable with numa enabled */
> 	BUG_ON(!pfn_valid(page_to_pfn(new_page)));
> #endif
> 	pageable = !PageReserved(new_page);
> 	as = !!new_page->mapping;
> 
> 	BUG_ON(!pageable && as);
> 
> 	pageable &= as;
> 
> 	/* ->nopage cannot return swapcache */
> 	BUG_ON(PageSwapCache(new_page));
> 	/* ->nopage cannot return anonymous pages */
> 	BUG_ON(PageAnon(new_page));
> 
> compare that with mainline...
> 
> I hope this incident will be enough to resurrect some of the
> "sanitized" bugchecks.

Well I added VM_BUG_ON so that we could keep the checks even just for
the value of commenting the code, and those who want to run without
them can choose to. However I may have put too much stuff under
CONFIG_DEBUG_VM which might discourage distros from turning it on.
I'll work on that...

> > wonder if I'm correct in thinking that checking the page index and mapping
> > is not actually racy?
> 
> Index and mapping shouldn't change if the page is locked, and you
> already added the BUG_ON(!PageLocked(page)).

I believe that's the case, yes.

--
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>

  reply	other threads:[~2007-02-15  0:46 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 [this message]
2007-02-14 16:52 ` Balbir Singh

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=20070215004638.GF29797@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=andrea@suse.de \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.org \
    --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).