mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Cc: "Mike Christie" <michaelc@cs.wisc.edu>
Subject: Possible memory leak in block/ll_rw_blk.c
Date: Sat, 9 Dec 2006 23:16:04 +0000	[thread overview]
Message-ID: <b0943d9e0612091516s600d2c5bp327ce5008a57381e@mail.gmail.com> (raw)

Hi,

After 2.6.19, kmemleak reports several (few tens) orphan blocks
allocated in bio_alloc_bioset() via __blk_rq_map_user() in
block/ll_rq_blk.c. I think these came with commit
0e75f9063f5c55fb0b0b546a7c356f8ec186825e (support larger block pc
requests). The allocation backtrace for the "bio" structure is:

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

Because the above objects cannot be tracked, kmemleak also reports the
bio_map_data structures allocated in bio_alloc_map_data (called from
bio_copy_user via the above backtrace).

Thanks.

-- 
Catalin

             reply	other threads:[~2006-12-09 23:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-09 23:16 Catalin Marinas [this message]
2006-12-13 10:00 ` Catalin Marinas
2006-12-13 12:45   ` FUJITA Tomonori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b0943d9e0612091516s600d2c5bp327ce5008a57381e@mail.gmail.com \
    --to=catalin.marinas@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®