[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4FBE243F.3080002@parallels.com>
Date: Thu, 24 May 2012 16:06:23 +0400
From: Glauber Costa <glommer@...allels.com>
To: Dave Chinner <david@...morbit.com>
CC: Christoph Lameter <cl@...ux.com>,
James Bottomley <James.Bottomley@...senPartnership.com>,
David Rientjes <rientjes@...gle.com>,
<linux-kernel@...r.kernel.org>, <cgroups@...r.kernel.org>,
<linux-mm@...ck.org>, Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: [PATCH] slab+slob: dup name string
On 05/24/2012 04:18 AM, Dave Chinner wrote:
>> Of course reasoning about why it was added helps (so let's try to
>> > determine that), but so far the only reasonably strong argument in
>> > favor of keeping it was robustness.
> I'm pretty sure it was added because there are slab names
> constructed by snprintf on a stack buffer, so the name doesn't exist
> beyond the slab initialisation function call...
>
> Cheers,
>
> Dave.
If that was the reason, we'd be seeing slab failing miserably where slub
succeeds, since slab keeps no copy.
--
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/
Powered by blists - more mailing lists