From: Nick Piggin <npiggin@suse.de>
To: linux-arch@vger.kernel.org,
linux-arm-kernel@lists.arm.linux.org.uk, rmk@arm.linux.org.uk,
Andrew Morton <akpm@linux-foundation.org>,
radford@blackbean.org
Subject: Re: [patch] mm: vmalloc fix lazy unmapping cache aliasing
Date: Wed, 19 Nov 2008 05:54:25 +0100 [thread overview]
Message-ID: <20081119045425.GB18697@wotan.suse.de> (raw)
In-Reply-To: <20081119045338.GA18697@wotan.suse.de>
Added Jim to CC...
On Wed, Nov 19, 2008 at 05:53:38AM +0100, Nick Piggin wrote:
>
> Jim Radford has reported that the vmap subsystem rewrite was sometimes causing
> his VIVT ARM system to behave strangely (seemed like going into infinite loops
> trying to fault in pages to userspace).
>
> We determined that the problem was most likely due to a cache aliasing issue.
> flush_cache_vunmap was only being called at the moment the page tables were
> to be taken down, however with lazy unmapping, this can happen after the page
> has subsequently been freed and allocated for something else. The dangling
> alias may still have dirty data attached to it.
>
> The fix for this problem is to do the cache flushing when the caller has
> called vunmap -- it would be a bug for them to write anything else to the
> mapping at that point.
>
> That appeared to solve Jim's problems.
>
> Reported-by: Jim Radford <radford@blackbean.org>
> Signed-off-by: Nick Piggin <npiggin@suse.de>
> ---
> Index: linux-2.6/mm/vmalloc.c
> ===================================================================
> --- linux-2.6.orig/mm/vmalloc.c
> +++ linux-2.6/mm/vmalloc.c
> @@ -77,7 +77,6 @@ static void vunmap_page_range(unsigned l
>
> BUG_ON(addr >= end);
> pgd = pgd_offset_k(addr);
> - flush_cache_vunmap(addr, end);
> do {
> next = pgd_addr_end(addr, end);
> if (pgd_none_or_clear_bad(pgd))
> @@ -543,9 +542,10 @@ static void purge_vmap_area_lazy(void)
> }
>
> /*
> - * Free and unmap a vmap area
> + * Free and unmap a vmap area, caller ensuring flush_cache_vunmap had been
> + * called for the correct range previously.
> */
> -static void free_unmap_vmap_area(struct vmap_area *va)
> +static void free_unmap_vmap_area_noflush(struct vmap_area *va)
> {
> va->flags |= VM_LAZY_FREE;
> atomic_add((va->va_end - va->va_start) >> PAGE_SHIFT, &vmap_lazy_nr);
> @@ -553,6 +553,15 @@ static void free_unmap_vmap_area(struct
> try_purge_vmap_area_lazy();
> }
>
> +/*
> + * Free and unmap a vmap area
> + */
> +static void free_unmap_vmap_area(struct vmap_area *va)
> +{
> + flush_cache_vunmap(va->va_start, va->va_end);
> + free_unmap_vmap_area_noflush(va);
> +}
> +
> static struct vmap_area *find_vmap_area(unsigned long addr)
> {
> struct vmap_area *va;
> @@ -734,7 +743,7 @@ static void free_vmap_block(struct vmap_
> spin_unlock(&vmap_block_tree_lock);
> BUG_ON(tmp != vb);
>
> - free_unmap_vmap_area(vb->va);
> + free_unmap_vmap_area_noflush(vb->va);
> call_rcu(&vb->rcu_head, rcu_free_vb);
> }
>
> @@ -820,6 +829,8 @@ static void vb_free(const void *addr, un
> free_vmap_block(vb);
> } else
> spin_unlock(&vb->lock);
> +
> + flush_cache_vunmap((unsigned long)addr, (unsigned long)addr + size);
> }
>
> /**
next prev parent reply other threads:[~2008-11-19 4:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 4:53 [patch] mm: vmalloc fix lazy unmapping cache aliasing Nick Piggin
2008-11-19 4:54 ` Nick Piggin [this message]
2008-11-19 18:58 ` Jim Radford
2008-11-19 20:17 ` Russell King
2008-11-20 2:17 ` Nick Piggin
2008-11-20 18:43 ` Catalin Marinas
2008-11-20 18:43 ` Catalin Marinas
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=20081119045425.GB18697@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=radford@blackbean.org \
--cc=rmk@arm.linux.org.uk \
/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