une 10, 2015 5:49 PM
To: Zhang, Yanmin
Cc: Christoph Lameter; Liu, XinwuX; penb...@kernel.org; m...@selenic.com;
linux...@kvack.org; linux-kernel@vger.kernel.org; He, Bo; Chen, Lin Z
Subject: Re: [PATCH] slub/slab: fix kmemleak didn't work on some case
On Wed, Jun 10, 2015 at 08:45:50AM +0100, Zhang,
...@kernel.org; m...@selenic.com;
linux...@kvack.org; linux-kernel@vger.kernel.org; He, Bo; Chen, Lin Z
Subject: Re: [PATCH] slub/slab: fix kmemleak didn't work on some case
On Wed, Jun 10, 2015 at 08:45:50AM +0100, Zhang, Yanmin wrote:
On 2015/6/9 23:03, Catalin Marinas wrote:
On Tue, Jun 09, 2015 at 09
On Wed, Jun 10, 2015 at 08:45:50AM +0100, Zhang, Yanmin wrote:
> On 2015/6/9 23:03, Catalin Marinas wrote:
> > On Tue, Jun 09, 2015 at 09:10:45AM +0100, Zhang, Yanmin wrote:
> >> On 2015/6/8 18:13, Catalin Marinas wrote:
> >>> As I replied already, I don't think this is that bad, or at least not
>
On 2015/6/9 23:03, Catalin Marinas wrote:
> On Tue, Jun 09, 2015 at 09:10:45AM +0100, Zhang, Yanmin wrote:
>> On 2015/6/8 18:13, Catalin Marinas wrote:
>>> As I replied already, I don't think this is that bad, or at least not
>>> worse than what kmemleak already does (looking at all data whether
On Wed, Jun 10, 2015 at 08:45:50AM +0100, Zhang, Yanmin wrote:
On 2015/6/9 23:03, Catalin Marinas wrote:
On Tue, Jun 09, 2015 at 09:10:45AM +0100, Zhang, Yanmin wrote:
On 2015/6/8 18:13, Catalin Marinas wrote:
As I replied already, I don't think this is that bad, or at least not
worse
On 2015/6/9 23:03, Catalin Marinas wrote:
On Tue, Jun 09, 2015 at 09:10:45AM +0100, Zhang, Yanmin wrote:
On 2015/6/8 18:13, Catalin Marinas wrote:
As I replied already, I don't think this is that bad, or at least not
worse than what kmemleak already does (looking at all data whether it's
On Tue, Jun 09, 2015 at 09:10:45AM +0100, Zhang, Yanmin wrote:
> On 2015/6/8 18:13, Catalin Marinas wrote:
> > As I replied already, I don't think this is that bad, or at least not
> > worse than what kmemleak already does (looking at all data whether it's
> > pointer or not).
>
> It depends. As
On 2015/6/8 18:13, Catalin Marinas wrote:
> On Mon, Jun 08, 2015 at 10:38:13AM +0100, Christoph Lameter wrote:
>> On Mon, 8 Jun 2015, Liu, XinwuX wrote:
>>
>>> when kernel uses kmalloc to allocate memory, slub/slab will find
>>> a suitable kmem_cache. Ususally the cache's object size is often
>>>
On 2015/6/8 18:13, Catalin Marinas wrote:
On Mon, Jun 08, 2015 at 10:38:13AM +0100, Christoph Lameter wrote:
On Mon, 8 Jun 2015, Liu, XinwuX wrote:
when kernel uses kmalloc to allocate memory, slub/slab will find
a suitable kmem_cache. Ususally the cache's object size is often
greater than
On Tue, Jun 09, 2015 at 09:10:45AM +0100, Zhang, Yanmin wrote:
On 2015/6/8 18:13, Catalin Marinas wrote:
As I replied already, I don't think this is that bad, or at least not
worse than what kmemleak already does (looking at all data whether it's
pointer or not).
It depends. As for
On Mon, Jun 08, 2015 at 10:38:13AM +0100, Christoph Lameter wrote:
> On Mon, 8 Jun 2015, Liu, XinwuX wrote:
>
> > when kernel uses kmalloc to allocate memory, slub/slab will find
> > a suitable kmem_cache. Ususally the cache's object size is often
> > greater than requested size. There is unused
On Mon, Jun 08, 2015 at 06:14:32AM +0100, Liu, XinwuX wrote:
> when kernel uses kmalloc to allocate memory, slub/slab will find
> a suitable kmem_cache. Ususally the cache's object size is often
> greater than requested size. There is unused space which contains
> dirty data. These dirty data
On Mon, 8 Jun 2015, Liu, XinwuX wrote:
> when kernel uses kmalloc to allocate memory, slub/slab will find
> a suitable kmem_cache. Ususally the cache's object size is often
> greater than requested size. There is unused space which contains
> dirty data. These dirty data might have pointers
On Mon, Jun 08, 2015 at 06:14:32AM +0100, Liu, XinwuX wrote:
when kernel uses kmalloc to allocate memory, slub/slab will find
a suitable kmem_cache. Ususally the cache's object size is often
greater than requested size. There is unused space which contains
dirty data. These dirty data might
On Mon, Jun 08, 2015 at 10:38:13AM +0100, Christoph Lameter wrote:
On Mon, 8 Jun 2015, Liu, XinwuX wrote:
when kernel uses kmalloc to allocate memory, slub/slab will find
a suitable kmem_cache. Ususally the cache's object size is often
greater than requested size. There is unused space
On Mon, 8 Jun 2015, Liu, XinwuX wrote:
when kernel uses kmalloc to allocate memory, slub/slab will find
a suitable kmem_cache. Ususally the cache's object size is often
greater than requested size. There is unused space which contains
dirty data. These dirty data might have pointers pointing
16 matches
Mail list logo
