From: Johannes Weiner <jweiner@redhat.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: linux-mm@kvack.org, Mel Gorman <mel@csn.ul.ie>,
Rik van Riel <riel@redhat.com>, Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH] THP: mremap support and TLB optimization #2
Date: Fri, 5 Aug 2011 12:50:47 +0200 [thread overview]
Message-ID: <20110805105047.GA32064@redhat.com> (raw)
In-Reply-To: <20110728142631.GI3087@redhat.com>
On Thu, Jul 28, 2011 at 04:26:31PM +0200, Andrea Arcangeli wrote:
> Hello,
>
> this is the latest version of the mremap THP native implementation
> plus optimizations.
>
> So first question is: am I right, the "- 1" that I am removing below
> was buggy? It's harmless because these old_end/next are page aligned,
> but if PAGE_SIZE would be 1, it'd break, right? It's really confusing
> to read even if it happens to work. Please let me know because that "-
> 1" ironically it's the thing I'm less comfortable about in this patch.
> @@ -134,14 +126,17 @@ unsigned long move_page_tables(struct vm
> {
> unsigned long extent, next, old_end;
> pmd_t *old_pmd, *new_pmd;
> + bool need_flush = false;
>
> old_end = old_addr + len;
> flush_cache_range(vma, old_addr, old_end);
>
> + mmu_notifier_invalidate_range_start(vma->vm_mm, old_addr, old_end);
> +
> for (; old_addr < old_end; old_addr += extent, new_addr += extent) {
> cond_resched();
> next = (old_addr + PMD_SIZE) & PMD_MASK;
> - if (next - 1 > old_end)
> + if (next > old_end)
> next = old_end;
If old_addr + PMD_SIZE overflows, next will be zero, thus smaller than
old_end and not fixed up. This results in a bogus extent length here:
> extent = next - old_addr;
which I think can overrun old_addr + len if the extent should have
actually been smaller than the distance between new_addr and the next
PMD as well as that LATENCY_LIMIT to which extent is capped a few
lines below. I haven't checked all the possibilities, though.
It could probably be
if (next > old_end || next - 1 > old_end)
next = old_end
to catch the theoretical next == old_end + 1 case, but PAGE_SIZE > 1
looks like a sensible assumption to me.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-08-05 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 14:26 [PATCH] THP: mremap support and TLB optimization #2 Andrea Arcangeli
2011-08-04 15:32 ` Andrea Arcangeli
2011-08-05 10:50 ` Johannes Weiner [this message]
2011-08-05 15:52 ` Andrea Arcangeli
2011-08-05 15:25 ` Mel Gorman
2011-08-05 16:21 ` Andrea Arcangeli
2011-08-05 17:11 ` Mel Gorman
2011-08-05 18:18 ` Andrea Arcangeli
2011-08-06 16:31 ` 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=20110805105047.GA32064@redhat.com \
--to=jweiner@redhat.com \
--cc=aarcange@redhat.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=riel@redhat.com \
/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.