From: Mike Snitzer <snitzer@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Alasdair Kergon <agk@redhat.com>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: dm-bufio: fix memleak when using a dm_buffer's inline bio
Date: Tue, 25 Nov 2014 22:41:04 -0500 [thread overview]
Message-ID: <20141126034103.GA26585@redhat.com> (raw)
In-Reply-To: <20141126014515.GE10050@birch.djwong.org>
On Tue, Nov 25 2014 at 8:45pm -0500,
Darrick J. Wong <darrick.wong@oracle.com> wrote:
> When dm-bufio sets out to use the bio built into a struct dm_buffer to
> issue an IO, it needs to call bio_reset after it's done with the bio
> so that we can free things attached to the bio such as the integrity
> payload. Therefore, inject our own endio callback to take care of
> the bio_reset after calling submit_io's end_io callback.
>
> Test case:
> 1. modprobe scsi_debug delay=0 dif=1 dix=199 ato=1 dev_size_mb=300
> 2. Set up a dm-bufio client, e.g. dm-verity, on the scsi_debug device
> 3. Repeatedly read metadata and watch kmalloc-192 leak!
>
> Fix is against 3.18-rc6.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Thanks for reporting/fixing this.
Alternatively I think we could just call bio_reset() in submit_io(),
e.g.:
diff --git a/drivers/md/dm-bufio.c b/drivers/md/dm-bufio.c
index afe7971..e7036e3 100644
--- a/drivers/md/dm-bufio.c
+++ b/drivers/md/dm-bufio.c
@@ -579,6 +579,8 @@ static void submit_io(struct dm_buffer *b, int rw, sector_t block,
if (rw == WRITE && b->c->write_callback)
b->c->write_callback(b);
+ bio_reset(&b->bio);
+
if (b->c->block_size <= DM_BUFIO_INLINE_VECS * PAGE_SIZE &&
b->data_mode != DATA_MODE_VMALLOC)
use_inline_bio(b, rw, block, end_io);
What do you think?
next prev parent reply other threads:[~2014-11-26 3:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 1:45 [PATCH] " Darrick J. Wong
2014-11-26 3:41 ` Mike Snitzer [this message]
2014-11-26 4:00 ` [dm-devel] " Darrick J. Wong
2014-11-26 14:28 ` Mike Snitzer
2014-11-26 15:09 ` Mike Snitzer
2014-11-26 17:28 ` [dm-devel] " Darrick J. Wong
2014-12-01 16:23 ` [dm-devel] [PATCH] " Mikulas Patocka
2014-12-01 16:27 ` Mike Snitzer
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=20141126034103.GA26585@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome