Re: [PATCH 00/10] Kernel memory leak detector 0.8

[Xiaolan Zhang]

Hi, Catalin,

I have identified the problem and will submit a fix soon.  Could you let 
me know to which tree should I apply the fix against?

thanks,
Catherine

"Catalin Marinas" <catalin.marinas@xxxxxxxxx> wrote on 07/12/2006 06:33:54 
AM:

> Hi Catherine,
> 
> On 11/07/06, Michal Piotrowski <michal.k.k.piotrowski@xxxxxxxxx> wrote:
> > This is most common
> > orphan pointer 0xf5a6fd60 (size 39):
> >   c0173822: <__kmalloc>
> >   c01df500: <context_struct_to_string>
> >   c01df679: <security_sid_to_context>
> >   c01d7eee: <selinux_socket_getpeersec_dgram>
> >   f884f019: <unix_get_peersec_dgram>
> >   f8850698: <unix_dgram_sendmsg>
> >   c02a88c2: <sock_sendmsg>
> >   c02a9c7a: <sys_sendto>
> >
> > cat /tmp/ml.txt | grep -c selinux_socket_getpeersec_dgram
> > 8442
> 
> I'm looking into the above leak report from kmemleak (the back trace
> to the kmalloc function). The "datagram getpeersec" patch went in as
> commit 877ce7c1b3afd69a9b1caeb1b9964c992641f52a. Have you noticed any
> abnormal increase in the slab statistics (especially size-64)?
> 
> Thanks.
> 
> -- 
> Catalin

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/