linux-kernel - Re: [patch 1/2] From: Paul Mundt <lethal@...ux-sh.org>

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: <20070511113915.267bcc66.akpm@linux-foundation.org>
Date:	Fri, 11 May 2007 11:39:15 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	clameter@....com
Cc:	linux-kernel@...r.kernel.org, Paul Mundt <lethal@...ux-sh.org>
Subject: Re: [patch 1/2] From: Paul Mundt <lethal@...ux-sh.org>

On Fri, 11 May 2007 09:57:50 -0700
clameter@....com wrote:

> > I'll take a look at tidying up the PMB slab, getting rid of the dtor
> > shouldn't be terribly painful. I simply opted to do the list management
> > there since others were doing it for the PGD slab cache at the time that
> > was written.
> 
> And here's the bit for dropping pmb_cache_dtor(), moving the list
> management up to pmb_alloc() and pmb_free().
> 
> With this applied, we're all set for killing off slab destructors
> from the kernel entirely.

hm, this is already in Paul's git tree.

If we're going to slam all this into 2.6.22 then I can just tempdrop Paul's
tree.

However I think we've done enough slab work for 2.6.22 now so I'm inclined
to queue these changes for 2.6.23.  That would mean that the slab changes in
-mm have a dependency on the sh git tree which I am sure to forget about.
If I end up merging these changes before Paul merges his tree, sh will
break.  Presumably Paul will notice 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/