All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Shaun Tancheff <shaun@tancheff.com>, linux-block@vger.kernel.org
Cc: Christoph Hellwig <hch@lst.de>,
	David Drysdale <drysdale@google.com>,
	Xiong Zhou <xzhou@redhat.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-nvdimm@ml01.01.org,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Catalin Marinas <catalin.marinas@arm.com>,
	LKML <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@fb.com>,
	bart.vanassche@sandisk.com,
	Shaun Tancheff <shaun.tancheff@seagate.com>
Subject: Re: [PATCH] Missing bio_put following submit_bio_wait
Date: Tue, 7 Jun 2016 10:48:15 -0600	[thread overview]
Message-ID: <5756FACF.8030202@kernel.dk> (raw)
In-Reply-To: <1465317133-13266-1-git-send-email-shaun@tancheff.com>

On 06/07/2016 10:32 AM, Shaun Tancheff wrote:
> submit_bio_wait() gives the caller an opportunity to examine
> struct bio and so expects the caller to issue the put_bio()
>
> This fixes a memory leak reported by a few people in 4.7-rc2
> kmemleak report after 9082e87bfbf8 ("block: remove struct bio_batch")
>
> Signed-off-by: Shaun Tancheff <shaun.tancheff@seagate.com>
> Tested-by: Catalin Marinas <catalin.marinas@arm.com>
> Tested-by: Larry Finger@lwfinger.net
> Tested-by: David Drysdale <drysdale@google.com>

Thanks, applied.

-- 
Jens Axboe

  parent reply	other threads:[~2016-06-07 16:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07 16:23 [PATCH] Fix reported kmemleak Shaun Tancheff
2016-06-07 16:32 ` [PATCH] Missing bio_put following submit_bio_wait Shaun Tancheff
2016-06-07 16:46   ` Christoph Hellwig
2016-06-07 16:48   ` Jens Axboe [this message]
2016-06-12 10:29 ` [PATCH] Fix reported kmemleak Xiong Zhou

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=5756FACF.8030202@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Larry.Finger@lwfinger.net \
    --cc=axboe@fb.com \
    --cc=bart.vanassche@sandisk.com \
    --cc=catalin.marinas@arm.com \
    --cc=drysdale@google.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-nvdimm@ml01.01.org \
    --cc=sfr@canb.auug.org.au \
    --cc=shaun.tancheff@seagate.com \
    --cc=shaun@tancheff.com \
    --cc=xzhou@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.