linux-kernel - Re: [GIT PULL] SLAB changes for v3.9-rc1

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]

Message-ID: <CAOJsxLFVKXPTuDgjB5nsjWqMe2rib5OdeE1sqBT_pgOqzGb5_Q@mail.gmail.com>
Date:	Wed, 6 Mar 2013 22:40:52 +0200
From:	Pekka Enberg <penberg@...nel.org>
To:	Christoph Lameter <cl@...ux.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] SLAB changes for v3.9-rc1

Hi Christoph,

On Wed, Mar 6, 2013 at 6:38 PM, Christoph Lameter <cl@...ux.com> wrote:
> Well this stuff was already ready for 3.8 and missed that merge period as
> well. There are a couple of bug fixes included as well. It is the basis
> for more common code between allocators. Most of it is renaming things so
> that fields have a common name which enables more code sharing.

It was me who missed the merge window - sorry about that. But is there
really any real need to push this through at such late stage? People
will work on "slab/next" branch anyway so what's the rush?

We had quite a lot of changes due to slab memcg and I'd rather keep
things calm for this release cycle. It usually takes a few cycles for
people to start noticing problems and it doesn't really help if
there's code churn going on all the time.

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