On 07/08/2015 01:17 AM, Christoph Hellwig wrote:
On Tue, Jul 07, 2015 at 06:59:37AM -0700, Bart Van Assche wrote:
Please note that my test was run with CONFIG_SLUB_DEBUG=y which causes a red
zone to be allocated before and after each block of allocated memory. Could
that explain the kmalloc-96 objects ?
96 is almost guaranteed to be the sense buffer allocated in
scsi_init_request and freed in scsi_exit_request.
Hello Catalin and Christoph,
kmemleak still reports large numbers of unreferenced objects for the
scsi-mq code with the v4.2-rc4 kernel even with the recently posted
scsi-mq leak fix applied on top of v4.2-rc4. Here is an example of one
such report:
unreferenced object 0xffff88045e05dc28 (size 96):
comm "srp_daemon", pid 8461, jiffies 4294973034 (age 742.350s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff814f2ede>] kmemleak_alloc+0x4e/0xb0
[<ffffffff811b0678>] kmem_cache_alloc_trace+0xc8/0x2d0
[<ffffffffa006cc37>] scsi_init_request+0x27/0x40 [scsi_mod]
[<ffffffff81278b91>] blk_mq_init_rq_map+0x1d1/0x260
[<ffffffff81278cc4>] blk_mq_alloc_tag_set+0xa4/0x1f0
[<ffffffffa006fb0d>] scsi_mq_setup_tags+0xcd/0xd0 [scsi_mod]
[<ffffffffa0066464>] scsi_add_host_with_dma+0x74/0x2e0 [scsi_mod]
[<ffffffffa0478e12>] srp_create_target+0xe12/0x1320 [ib_srp]
[<ffffffff8138a728>] dev_attr_store+0x18/0x30
[<ffffffff812371f8>] sysfs_kf_write+0x48/0x60
[<ffffffff812367f4>] kernfs_fop_write+0x144/0x190
[<ffffffff811bdaf8>] __vfs_write+0x28/0xe0
[<ffffffff811be1a9>] vfs_write+0xa9/0x190
[<ffffffff811bef09>] SyS_write+0x49/0xa0
[<ffffffff815022f2>] entry_SYSCALL_64_fastpath+0x16/0x7a
[<ffffffffffffffff>] 0xffffffffffffffff
Thanks,
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
