linux-kernel - Re: [PATCH] Ensure that walk_page_range()'s start and end are page-aligned

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 13 Feb 2012 13:55:31 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	Dan Smith <danms@...ibm.com>
cc:	akpm@...ux-foundation.org, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Ensure that walk_page_range()'s start and end are
 page-aligned

On Mon, 13 Feb 2012, Dan Smith wrote:

> DR> It doesn't "ensure" anything without CONFIG_DEBUG_VM enabled, which
> DR> isn't the default.
> 
> Are you proposing a change in verbiage or a stronger check? A
> VM_BUG_ON() seemed on par with other checks, such as the one in
> get_user_pages_fast().
> 

That's not a precedent, there's a big difference between the performance 
of gup_fast(), where we can't spare an additional compare and branch, and 
walk_page_range().  VM_BUG_ON() is typically used in situations where a 
debug kernel has been built, including CONFIG_DEBUG_VM, and the check 
helps to isolate a problem that would be otherwise difficult to find.  If 
that fits the criteria, fine, but it doesn't "ensure" walk_page_range() 
always has start and end addresses that are page aligned, so the changelog 
needs to be modified to describe why an error in this path wouldn't be 
evident.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/