linux-kernel - Re: [ 31/82] mm/vmalloc.c: change void* into explict vm

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: <alpine.DEB.2.00.1206080341050.4994@chino.kir.corp.google.com>
Date:	Fri, 8 Jun 2012 03:41:57 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Ben Hutchings <ben@...adent.org.uk>
cc:	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	alan@...rguk.ukuu.org.uk, Minchan Kim <minchan@...nel.org>
Subject: Re: [ 31/82] mm/vmalloc.c: change void* into explict vm_struct*

On Fri, 8 Jun 2012, Ben Hutchings wrote:

> 3.2-stable review patch.  If anyone has any objections, please let me know.
> 
> ------------------
> 
> From: Minchan Kim <minchan@...nel.org>
> 
> commit db1aecafef58b5dda39c4228debe2c845e4a27ab upstream.
> 
> vmap_area->private is void* but we don't use the field for various purpose
> but use only for vm_struct.  So change it to a vm_struct* with naming to
> improve for readability and type checking.
> 
> Signed-off-by: Minchan Kim <minchan@...nel.org>
> Acked-by: David Rientjes <rientjes@...gle.com>
> Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>
> Signed-off-by: Linus Torvalds <torvalds@...ux-foundation.org>
> Signed-off-by: Ben Hutchings <ben@...adent.org.uk>

I'm not sure this is stable material and it wasn't annotated as such when 
it was commited, why should someone need to upgrade their 3.2 for a patch 
like this?
--
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/