All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: do we want to kill VM_RESERVED or not? [was Re: 2.6.5-rc1-aa3]
Date: Tue, 23 Mar 2004 10:54:38 +0100	[thread overview]
Message-ID: <200403231054.38582@WOLK> (raw)
In-Reply-To: <20040322124257.GT3649@dualathlon.random>

On Monday 22 March 2004 13:42, Andrea Arcangeli wrote:

Hi Andrea,

> I see, the below patch will avoid your oops (I also removed the stack
> trace dump from memory.c since it's useless to get the stack trace from
> there and this will reduce the noise).
> --- x/mm/memory.c.~1~	2004-03-21 15:21:42.000000000 +0100
> +++ x/mm/memory.c	2004-03-22 13:40:26.852849384 +0100
> @@ -324,9 +324,11 @@ skip_copy_pte_range:
>  					 * Device driver pages must not be
>  					 * tracked by the VM for unmapping.
>  					 */
> -					BUG_ON(!page_mapped(page));
> -					BUG_ON(!page->mapping);
> -					page_add_rmap(page, vma, address, PageAnon(page));
> +					if (likely(page_mapped(page) && page->mapping))
> +						page_add_rmap(page, vma, address, PageAnon(page));
> +					else
> +						printk("Badness in %s at %s:%d\n",
> +						       __FUNCTION__, __FILE__, __LINE__);
>  				} else {
>  					BUG_ON(page_mapped(page));
>  					BUG_ON(page->mapping);
> @@ -1429,7 +1431,9 @@ retry:
>  	 * real anonymous pages, they're "device" reserved pages instead.
>  	 */
>  	reserved = !!(vma->vm_flags & VM_RESERVED);
> -	WARN_ON(reserved == pageable);
> +	if (unlikely(reserved == pageable))
> +		printk("Badness in %s at %s:%d\n",
> +		       __FUNCTION__, __FILE__, __LINE__);
>
>  	/*
>  	 * Should we do an early C-O-W break?

Perfect. Thanks alot.


> many thanks for the help!

You're welcome. Thanks for your help!

ciao, Marc

  reply	other threads:[~2004-03-23  9:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-20 21:03 2.6.5-rc1-aa3 Andrea Arcangeli
2004-03-20 22:06 ` 2.6.5-rc1-aa3 Andrew Morton
2004-03-21  6:17 ` 2.6.5-rc1-aa3 Martin J. Bligh
2004-03-21 11:51   ` 2.6.5-rc1-aa3 Andrea Arcangeli
2004-03-21 13:26   ` 2.6.5-rc1-aa3 Andrea Arcangeli
2004-03-21 16:23     ` 2.6.5-rc1-aa3 Martin J. Bligh
2004-03-21 10:05 ` 2.6.5-rc1-aa3 Marc-Christian Petersen
2004-03-21 11:49   ` do we want to kill VM_RESERVED or not? [was Re: 2.6.5-rc1-aa3] Andrea Arcangeli
2004-03-21 12:00     ` Andrea Arcangeli
2004-03-21 12:15       ` Andrea Arcangeli
2004-03-21 19:42         ` Marc-Christian Petersen
2004-03-22  0:10           ` Andrea Arcangeli
2004-03-22 12:10             ` Marc-Christian Petersen
2004-03-22 12:42               ` Andrea Arcangeli
2004-03-23  9:54                 ` Marc-Christian Petersen [this message]
2004-03-21 23:24     ` Andrew Morton
2004-03-22  0:51       ` Andrea Arcangeli

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=200403231054.38582@WOLK \
    --to=m.c.p@wolk-project.de \
    --cc=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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.