linux-kernel - Re: [PATCH] mm: fix lazy vmap purging (use-after-free error)

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, 23 Feb 2009 12:30:45 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	paulmck@...ux.vnet.ibm.com
Cc:	nickpiggin@...oo.com.au, vegard.nossum@...il.com, mingo@...e.hu,
	stable@...nel.org, npiggin@...e.de, penberg@...helsinki.fi,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: fix lazy vmap purging (use-after-free error)

On Mon, 23 Feb 2009 12:12:36 -0800
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> wrote:
> > 
> > As I suggested before, please add a new state variable which is private
> > to your subsystem.  That way it remains isolated from other subsystems.
> 
> OK, so my thought would be to have a function call into RCU from either
> init_post() or from rest_init().  This function would then set a variable
> private to RCU.
> 
> Seem reasonable?
> 

If that flag will only be used by one flavour of RCU then that would be
a good way to go.

Otherwise, heck, just make it a global variable with a well-chosen name
and write to it directly.  Simple, perfectly clear and understandable..

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