public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org, hugh@veritas.com
Subject: Re: 2.6.5-rc2-aa5
Date: Mon, 29 Mar 2004 12:48:03 -0800	[thread overview]
Message-ID: <20040329124803.072bb7c6.akpm@osdl.org> (raw)
In-Reply-To: <20040329150646.GA3808@dualathlon.random>

Andrea Arcangeli <andrea@suse.de> wrote:
>
> Notably there is a BUG_ON(page->mapping) triggering in
> page_remove_rmap in the pagecache case. that could be ex-pagecache being
> removed from pagecache before all ptes have been zapped, infact the
> page_remove_rmap triggers in the vmtruncate path.

Confused.  vmtruncate zaps the ptes before removing pages from pagecache,
so I'd expect a non-null ->mapping in page_remove_rmap() is a very common
thing.  truncate a file which someone has mmapped and it'll happen every
time, will it not?


  reply	other threads:[~2004-03-29 20:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-29 15:06 2.6.5-rc2-aa5 Andrea Arcangeli
2004-03-29 20:48 ` Andrew Morton [this message]
2004-03-29 22:45   ` 2.6.5-rc2-aa5 Andrea Arcangeli
2004-03-30 16:10     ` mapped pages being truncated [was Re: 2.6.5-rc2-aa5] Andrea Arcangeli
2004-03-30 18:01       ` Hugh Dickins
2004-03-30 18:20         ` Andrea Arcangeli
2004-03-30 18:48           ` Hugh Dickins
2004-03-30 19:01             ` Andrea Arcangeli
2004-03-30 19:06               ` Hugh Dickins
2004-03-30 19:12                 ` Andrea Arcangeli
2004-03-30 18:28       ` Andrew Morton
2004-03-30 18:51         ` Andrea Arcangeli
2004-03-30 20:13         ` Nathan Scott
  -- strict thread matches above, loose matches on Subject: below --
2004-03-29 18:12 [RFC][PATCH 1/3] radix priority search tree - objrmap complexity fix Hugh Dickins
2004-03-29 21:30 ` 2.6.5-rc2-aa5 Rajesh Venkatasubramanian
2004-03-29 22:50   ` 2.6.5-rc2-aa5 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=20040329124803.072bb7c6.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox