linux-kernel - Re: [PATCH] [8/13] Enable the mask allocator for x86

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: <20080307190909.GA15512@uranus.ravnborg.org>
Date:	Fri, 7 Mar 2008 20:09:09 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH] [8/13] Enable the mask allocator for x86

On Fri, Mar 07, 2008 at 08:03:13PM +0100, Andi Kleen wrote:
> On Fri, Mar 07, 2008 at 07:32:55PM +0100, Sam Ravnborg wrote:
> > On Fri, Mar 07, 2008 at 10:07:18AM +0100, Andi Kleen wrote:
> > > 
> > > - Disable old ZONE_DMA
> > > No fixed size ZONE_DMA now anymore. All existing users of __GFP_DMA rely 
> > > on the compat call to the maskable allocator in alloc/free_pages
> > > - Call maskable allocator initialization functions at boot
> > > - Add TRAD_DMA_MASK for the compat functions 
> > 
> > I see TRAD_DMA_MASK used by patch 6 and patch 7, but only here
> > in this later patch it is defined.
> > Looks like we have build breakage - but I have not checked it.
> 
> It is only used when the architecture defines CONFIG_MASK_ALLOC and
> that is not done by any until the later patches.
Understood - I just took a quick look and wanted to let you know.

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