Re: Possible memory leak in block/ll_rw_blk.c

On 09/12/06, Catalin Marinas <[email protected]> wrote:

unreferenced object 0xdd9162b0 (size 64):
  [<c018d46f>] kmem_cache_alloc
  [<c0170b2e>] mempool_alloc_slab
  [<c01709cb>] mempool_alloc
  [<c01b7baa>] bio_alloc_bioset
  [<c01b7d0e>] bio_alloc
  [<c01b83f8>] bio_copy_user
  [<c021a380>] __blk_rq_map_user
  [<c021a4ff>] blk_rq_map_user
  [<c021e687>] sg_io
  [<c021ed3e>] scsi_cmd_ioctl
  [<c02bcc13>] sd_ioctl
  [<c021ca65>] blkdev_driver_ioctl
  [<c021cc27>] blkdev_ioctl
  [<c01ba72b>] block_ioctl
  [<c019ea36>] do_ioctl

I can confirm that the memory leak disappeared with commit
77d172ce2719b5ad2dc0637452c8871d9cba344c (by Fujita Tomonori).

Regards.

--
Catalin
-
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/

---

• Follow-Ups:
  • Re: Possible memory leak in block/ll_rw_blk.c
    • From: FUJITA Tomonori <[email protected]>

• References:
  • Possible memory leak in block/ll_rw_blk.c
    • From: "Catalin Marinas" <[email protected]>

• Prev by Date: Re: [patch 2/3] acpi: Add a docked sysfs file to the dock driver.
• Next by Date: Re: cfq performance gap
• Previous by thread: Possible memory leak in block/ll_rw_blk.c
• Next by thread: Re: Possible memory leak in block/ll_rw_blk.c
• 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]