From: Shaun Tancheff <shaun@tancheff.com>
To: linux-block@vger.kernel.org
Cc: Shaun Tancheff <shaun@tancheff.com>,
Christoph Hellwig <hch@lst.de>,
axboe@kernel.dk, 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
Subject: [PATCH] Fix reported kmemleak
Date: Tue, 7 Jun 2016 11:23:30 -0500 [thread overview]
Message-ID: <1465316612-9649-1-git-send-email-shaun@tancheff.com> (raw)
This fixes a memory leak reported by a few people in 4.7-rc1
kmemleak report after 9082e87bfbf8 ("block: remove struct bio_batch")
This patch just formalizes the one in this discussion here:
https://lkml.kernel.org/r/20160606112620.GA29910@e104818-lin.cambridge.arm.com
The same issue appears here:
https://lkml.kernel.org/r/20160607102651.GA6480@dhcp12-144.nay.redhat.com
Patch is also available at:
https://github.com/stancheff/linux.git
branch: v4.7-rc2+bio_put
Cc: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernel.dk
cc: David Drysdale <drysdale@google.com>
Cc: Xiong Zhou <xzhou@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Cc: linux-nvdimm@ml01.01.org
Cc: Christoph Hellwig <hch@lst.de>
Cc: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Cc: Jens Axboe <axboe@fb.com>,
Cc: bart.vanassche@sandisk.com
Shaun Tancheff (1):
Missing bio_put following submit_bio_wait
block/blk-lib.c | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
--
2.8.1
next reply other threads:[~2016-06-07 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 16:23 Shaun Tancheff [this message]
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
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=1465316612-9649-1-git-send-email-shaun@tancheff.com \
--to=shaun@tancheff.com \
--cc=Larry.Finger@lwfinger.net \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--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=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 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®