From: David Rientjes <rientjes@google.com>
To: Dan Smith <danms@us.ibm.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Ensure that walk_page_range()'s start and end are page-aligned
Date: Mon, 13 Feb 2012 02:12:21 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.00.1202130211400.4324@chino.kir.corp.google.com> (raw)
In-Reply-To: <1328902796-30389-1-git-send-email-danms@us.ibm.com>
On Fri, 10 Feb 2012, Dan Smith wrote:
> The inner function walk_pte_range() increments "addr" by PAGE_SIZE after
> each pte is processed, and only exits the loop if the result is equal to
> "end". Current, if either (or both of) the starting or ending addresses
> passed to walk_page_range() are not page-aligned, then we will never
> satisfy that exit condition and begin calling the pte_entry handler with
> bad data.
>
> To be sure that we will land in the right spot, this patch checks that
> both "addr" and "end" are page-aligned in walk_page_range() before starting
> the traversal.
>
It doesn't "ensure" anything without CONFIG_DEBUG_VM enabled, which isn't
the default.
--
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:[~2012-02-13 10:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 19:39 Dan Smith
2012-02-10 19:45 ` Michal Nazarewicz
2012-02-10 19:57 ` Dan Smith
2012-02-10 20:13 ` Michal Nazarewicz
2012-02-13 10:12 ` David Rientjes [this message]
2012-02-13 14:52 ` Dan Smith
2012-02-13 21:55 ` David Rientjes
2012-02-14 14:59 ` Dan Smith
2012-02-14 21:04 ` David Rientjes
2012-02-15 14:39 ` Dan Smith
2012-02-24 19:19 ` Dan Smith
2012-02-24 20:55 ` Andrew Morton
2012-02-24 21:03 ` Dan Smith
-- strict thread matches above, loose matches on Subject: below --
2012-02-10 15:53 Dan Smith
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=alpine.DEB.2.00.1202130211400.4324@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=danms@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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