public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: David Miller <davem@davemloft.net>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: [PATCH] fix update_mmu_cache in fremap.c
Date: Fri, 26 May 2006 22:43:47 +0000	[thread overview]
Message-ID: <Pine.LNX.4.64.0605262340130.9720@blonde.wat.veritas.com> (raw)
In-Reply-To: <20060526.131059.27783433.davem@davemloft.net>

On Fri, 26 May 2006, David Miller wrote:
> From: Hugh Dickins <hugh@veritas.com>
> Date: Fri, 26 May 2006 19:28:14 +0100 (BST)
> 
> > There are two calls to update_mmu_cache in fremap.c, both defective.
> > The one in install_page needs to be accompanied by lazy_mmu_prot_update
> > (some other cleanup time, move that into ia64 update_mmu_cache itself); and
> > the one in install_file_pte should be removed since the pte is not present.
> > 
> > Signed-off-by: Hugh Dickins <hugh@veritas.com>
> 
> Where did that rule come from?  We should call update_mmu_cache() even
> if the PTE was not present before, look at the fault path in
> mm/memory.c, it does this too.
> 
> This is where we install hash table entries for newly installed
> mappings on sparc64 and powerpc, so this update_mmu_cache() call
> is important even for not-previously-present mappings.

Sure it's important for not-previously-present mappings, when you're
installing a present pte.  But the "file pte" being installed by
install_file_pte is not a real pte - it's a non-present entry (like
a swap entry), noting what file offset should be mapped there when
there's a fault (in a non-linear vma where that's not obvious).

Hugh

  reply	other threads:[~2006-05-26 22:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-26 18:28 [PATCH] fix update_mmu_cache in fremap.c Hugh Dickins
2006-05-26 20:10 ` David Miller
2006-05-26 22:43   ` Hugh Dickins [this message]
2006-05-26 23:37     ` David Miller

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=Pine.LNX.4.64.0605262340130.9720@blonde.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=linux-ia64@vger.kernel.org \
    --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