From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, Joe Thornber <ejt@redhat.com>,
Alasdair G Kergon <agk@redhat.com>
Subject: [git pull] device mapper fixes for 4.4-rc5
Date: Fri, 11 Dec 2015 10:20:14 -0500 [thread overview]
Message-ID: <20151211152014.GA2751@redhat.com> (raw)
Hi Linus,
The following changes since commit 31ade3b83e1821da5fbb2f11b5b3d4ab2ec39db8:
Linux 4.4-rc3 (2015-11-29 18:58:26 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm tags/dm-4.4-fixes-2
for you to fetch changes up to ed8b45a3679eb49069b094c0711b30833f27c734:
dm btree: fix bufio buffer leaks in dm_btree_del() error path (2015-12-10 10:30:18 -0500)
Please pull, thanks!
Mike
----------------------------------------------------------------
Five stable fixes:
- Two DM btree bufio buffer leak fixes that resolve reported BUG_ONs
during DM thinp metadata close's dm_bufio_client_destroy().
- A DM thinp range discard fix to handle discarding a partially mapped
range.
- A DM thinp metadata snapshot fix to make sure the btree roots saved in
the metadata snapshot are the most current.
- A DM space map metadata refcounting fix that improves both DM thinp
and DM cache metadata.
----------------------------------------------------------------
Joe Thornber (4):
dm thin metadata: fix bug in dm_thin_remove_range()
dm thin metadata: fix bug when taking a metadata snapshot
dm space map metadata: fix ref counting bug when bootstrapping a new space map
dm btree: fix bufio buffer leaks in dm_btree_del() error path
Mike Snitzer (1):
dm btree: fix leak of bufio-backed block in btree_split_sibling error path
drivers/md/dm-thin-metadata.c | 34 ++++++-
drivers/md/persistent-data/dm-btree.c | 101 ++++++++++++++++++++-
drivers/md/persistent-data/dm-btree.h | 14 ++-
drivers/md/persistent-data/dm-space-map-metadata.c | 32 +++++--
4 files changed, 161 insertions(+), 20 deletions(-)
reply other threads:[~2015-12-11 15:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20151211152014.GA2751@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ejt@redhat.com \
--cc=torvalds@linux-foundation.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 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.