Re: More information on scsi_cmd_cache leak... (bisect)

I found a patch called: slab-leak-detector.patch and applied it (manually since it's for a slightly older kernel).

Here are the results: (after leaking about 1MB)

c03741ba <__scsi_get_command+0x29/0x73>

Is the leaker with 294 of them, vs 4 of:

c03743fd <scsi_setup_command_freelist+0xb0/0x101>

and 21:
fffffffe <0xfffffffe>

I'm not sure how helpful that result is though, since I guess we already knew it was scsi, and from the other email, that's it's also some interaction with md.

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

---

• References:
  • More information on scsi_cmd_cache leak... (bisect)
    • From: Chase Venters <[email protected]>

• Prev by Date: Re: traceroute bug ?
• Next by Date: Re: RCU latency regression in 2.6.16-rc1
• Previous by thread: Re: More information on scsi_cmd_cache leak... (bisect)
• Next by thread: $$s1> just ArtsandCulture
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]