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

["Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>]

Hi Catalin,

On 13/07/06, Catalin Marinas <catalin.marinas@gmail.com> wrote:
> On 12/07/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> > Please try something like this
> > on tty1
> > isic -s rand -d your ip (http://www.packetfactory.net/Projects/ISIC/)
> > on tty2
> > kml_collector (http://www.stardust.webpages.pl/files/o_bugs/kml/ml/kml_collector.sh)
> >
> > (I have tried to read random files from /sys on vanilla kernel, but I
> > can't reproduce that lockup)
>
> Couldn't get it on my (embedded) platform but I think that's because
> there are only a few reports in the memleak file. You have thousands
> of reports and I think reading the memleak file is causing the soft
> lockup.
>
> Until we identify the leak (or false positive), you can use the
> attached patch to supress the reports for context_struct_to_string.
> Hopefully, this should eliminate the soft lockup as well.

Thanks.

After applying context_struct_to_string-not-leak.patch and reverting
alloc_skb-false-positive.patch I haven't noticed that soft lockup.

Here is something new
orphan pointer 0xf40d61ac (size 1536):
 c017392a: <__kmalloc_track_caller>
 c01631b1: <__kzalloc>
 f98869cd: <skge_ring_alloc>
 f9888a1d: <skge_up>
 c02b17b6: <dev_open>
 c02b2e94: <dev_change_flags>
 c02e6e17: <devinet_ioctl>
 c02e8a02: <inet_ioctl>

http://www.stardust.webpages.pl/files/o_bugs/kml/ml2/
http://www.stardust.webpages.pl/files/o_bugs/kml/ml3/

After alloc_skb-false-positive.patch revert
http://www.stardust.webpages.pl/files/o_bugs/kml/ml4/

> --
> Catalin

Regards,
Michal

--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/