linux-kernel - Re: [PATCH 1/2] vmap: cope with vm_unmap_aliases before vmalloc

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] [day] [month] [year] [list]

Date:	Thu, 6 Nov 2008 15:51:32 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Nick Piggin <nickpiggin@...oo.com.au>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: [PATCH 1/2] vmap: cope with vm_unmap_aliases before
	vmalloc_init()


* Nick Piggin <nickpiggin@...oo.com.au> wrote:

> On Thursday 06 November 2008 21:02, Ingo Molnar wrote:
> > * Jeremy Fitzhardinge <jeremy@...p.org> wrote:
> > > Jeremy Fitzhardinge wrote:
> > >> Xen can end up calling vm_unmap_aliases() before vmalloc_init() has
> > >> been called.  In this case its safe to make it a simple no-op.
> > >>
> > >> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
> > >
> > > Ping?  Nick, Ingo: do you want to pick these up, or shall I send them to
> > > Linus myself?
> >
> > i've applied them to tip/core/urgent and will send them to Linus
> > unless Nick or Andrew has objections.
> 
> Thanks, yeah ack from me on those. I'm generally expecting Andrew to 
> pick up and merge mm patches, but I guess he wasn't cc'ed this time. 
> Anyway, if Ingo gets them upstream, that would be fine too.

linux-mm was Cc:-ed - but the crux of the changes was in Xen code, so 
i guess Andrew was looking at me and i was looking at him, expecting 
the other guy to do the work ;-)

anyway, it's all queued up and tested now.

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