All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: 4.1-rc2 dm-multipath-mq kernel warning
Date: Thu, 28 May 2015 10:19:55 +0200	[thread overview]
Message-ID: <5566CFAB.7060408@sandisk.com> (raw)
In-Reply-To: <20150527223741.GA18501@redhat.com>

On 05/28/15 00:37, Mike Snitzer wrote:
> FYI, I've staged a variant patch for 4.1 that is simpler; along with the
> various fixes I've picked up from Junichi and the leak fix I emailed
> earlier.  They are now in linux-next and available in this 'dm-4.1'
> specific branch (based on 4.1-rc5):
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/log/?h=dm-4.1
>
> Please try and let me know if your test works.

No data corruption was reported this time but a very large number of 
memory leaks were reported by kmemleak. The initiator system ran out of 
memory after some time due to these leaks. Here is an example of a leak 
reported by kmemleak:

unreferenced object 0xffff8800a39fc1a8 (size 96):
    comm "srp_daemon", pid 2116, jiffies 4294955508 (age 137.600s)
    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:
      [<ffffffff81600029>] kmemleak_alloc+0x49/0xb0
      [<ffffffff81167d19>] kmem_cache_alloc_node+0xd9/0x190
      [<ffffffff81425400>] scsi_init_request+0x20/0x40
      [<ffffffff812cbb98>] blk_mq_init_rq_map+0x228/0x290
      [<ffffffff812cbcc6>] blk_mq_alloc_tag_set+0xc6/0x220
      [<ffffffff81427488>] scsi_mq_setup_tags+0xc8/0xd0
      [<ffffffff8141e34f>] scsi_add_host_with_dma+0x6f/0x300
      [<ffffffffa04c62bf>] srp_create_target+0x11cf/0x1600 [ib_srp]
      [<ffffffff813f9c93>] dev_attr_store+0x13/0x20
      [<ffffffff81200a33>] sysfs_kf_write+0x43/0x60
      [<ffffffff811fff8b>] kernfs_fop_write+0x13b/0x1a0
      [<ffffffff81183e53>] __vfs_write+0x23/0xe0
      [<ffffffff81184524>] vfs_write+0xa4/0x1b0
      [<ffffffff811852d4>] SyS_write+0x44/0xb0
      [<ffffffff81613cdb>] system_call_fastpath+0x16/0x73
      [<ffffffffffffffff>] 0xffffffffffffffff

> I don't have SRP setup otherwise I'd try your reproducer you shared a
> while ago.  Any chance you're aware of a way to reproduce with LIO (and
> tcm utils)?

If I find a way to reproduce this with LIO I'll let you know.

Bart.

  reply	other threads:[~2015-05-28  8:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 14:04 4.1-rc2 dm-multipath-mq kernel warning Bart Van Assche
2015-05-06  2:23 ` Mike Snitzer
2015-05-06  7:45   ` Bart Van Assche
2015-05-06 18:29     ` Mike Snitzer
2015-05-07 10:19       ` Bart Van Assche
2015-05-27 12:57         ` Mike Snitzer
2015-05-27 15:29           ` Bart Van Assche
2015-05-27 15:33             ` Bart Van Assche
2015-05-27 16:14               ` Mike Snitzer
2015-05-27 17:00                 ` Mike Snitzer
2015-05-27 22:37                   ` Mike Snitzer
2015-05-28  8:19                     ` Bart Van Assche [this message]
2015-05-28 13:10                       ` Mike Snitzer
2015-05-28 14:07                         ` Mike Snitzer
2015-05-28 14:54                           ` Bart Van Assche
2015-05-28 15:06                             ` Mike Snitzer
2015-05-29 10:04                               ` Bart Van Assche

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=5566CFAB.7060408@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=dm-devel@redhat.com \
    --cc=hch@lst.de \
    --cc=snitzer@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.