From: David Miller <davem@davemloft.net>
To: Vineet.Gupta1@synopsys.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, mgorman@suse.de, hughd@google.com,
riel@redhat.com, rientjes@google.com, peterz@infradead.org,
linux-arch@vger.kernel.org, catalin.marinas@arm.com,
jcmvbkbc@gmail.com
Subject: Re: [PATCH] mm: Fix the TLB range flushed when __tlb_remove_page() runs out of slots
Date: Mon, 29 Jul 2013 16:41:06 -0700 (PDT) [thread overview]
Message-ID: <20130729.164106.943996066712571180.davem@davemloft.net> (raw)
In-Reply-To: <1369832173-15088-1-git-send-email-vgupta@synopsys.com>
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Date: Wed, 29 May 2013 18:26:13 +0530
> zap_pte_range loops from @addr to @end. In the middle, if it runs out of
> batching slots, TLB entries needs to be flushed for @start to @interim,
> NOT @interim to @end.
>
> Since ARC port doesn't use page free batching I can't test it myself but
> this seems like the right thing to do.
> Observed this when working on a fix for the issue at thread:
> http://www.spinics.net/lists/linux-arch/msg21736.html
>
> Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
As this bug can cause pretty serious memory corruption, I'd like to
see this submitted to -stable.
Thanks!
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-07-29 23:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 12:56 [PATCH] mm: Fix the TLB range flushed when __tlb_remove_page() runs out of slots Vineet Gupta
2013-05-29 14:03 ` Catalin Marinas
2013-05-29 14:08 ` Vineet Gupta
2013-05-29 14:29 ` Catalin Marinas
2013-05-29 14:36 ` Vineet Gupta
2013-05-29 14:51 ` Catalin Marinas
2013-05-30 5:02 ` Vineet Gupta
2013-07-29 23:41 ` David Miller [this message]
2013-07-29 23:46 ` Andrew Morton
2013-07-30 0:16 ` Greg KH
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=20130729.164106.943996066712571180.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Vineet.Gupta1@synopsys.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=hughd@google.com \
--cc=jcmvbkbc@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=rientjes@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).