linux-kernel - Re: [patch 1/5] vmalloc: do not check for freed locks on user maps

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]

Message-Id: <200803061334.58481.nickpiggin@yahoo.com.au>
Date:	Thu, 6 Mar 2008 13:34:58 +1100
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Greg KH <greg@...ah.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [patch 1/5] vmalloc: do not check for freed locks on user maps

On Thursday 06 March 2008 10:31, Thomas Gleixner wrote:
> On Thu, 6 Mar 2008, Nick Piggin wrote:

> > This is the kernel mapping. The user mapping is unmapped when
> > the userspace munmaps.
>
> Ok, my misinterpretation of that flag. Is the user space unmap in the
> same code path ? If yes, how can it be distinguished from the kernel
> space unmap ?

The flag I added so that the vmap can be passed to remap_vmalloc_range.
There were a couple of places at one point that were not zeroing out
the vmalloced memory correctly, so this just helps ensure we don't leak
data.

Userspace unmap is unmap_vmas and related code in mm/memory.c.

--
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/