From: Mike Snitzer <snitzer@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: dm-devel@redhat.com, Damien Le Moal <damien.lemoal@wdc.com>,
Alasdair G Kergon <agk@redhat.com>,
Shenghui Wang <shhuiw@foxmail.com>
Subject: [git pull] device mapper fixes for 4.19 final
Date: Wed, 10 Oct 2018 12:46:44 -0400 [thread overview]
Message-ID: <20181010164643.GA10173@redhat.com> (raw)
Hi Greg,
The following changes since commit 0238df646e6224016a45505d2c111a24669ebe21:
Linux 4.19-rc7 (2018-10-07 17:26:02 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-4.19/dm-fixes-3
for you to fetch changes up to beb9caac211c1be1bc118bb62d5cf09c4107e6a5:
dm linear: eliminate linear_end_io call if CONFIG_DM_ZONED disabled (2018-10-10 12:11:09 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix a DM cache module init error path bug that doesn't properly
cleanup a KMEM_CACHE if target registration fails.
- Two stable@ fixes for DM zoned target; 4.20 will have changes that
eliminate this code entirely but <= 4.19 needs these changes.
----------------------------------------------------------------
Damien Le Moal (1):
dm: fix report zone remapping to account for partition offset
Mike Snitzer (1):
dm linear: eliminate linear_end_io call if CONFIG_DM_ZONED disabled
Shenghui Wang (1):
dm cache: destroy migration_cache if cache target registration failed
drivers/md/dm-cache-target.c | 5 ++---
drivers/md/dm-linear.c | 8 +++++++-
drivers/md/dm.c | 27 ++++++++++++++++++++-------
3 files changed, 29 insertions(+), 11 deletions(-)
next reply other threads:[~2018-10-10 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 16:46 Mike Snitzer [this message]
2018-10-10 20:35 ` [git pull] device mapper fixes for 4.19 final Greg Kroah-Hartman
2018-10-11 3:37 ` [git pull] device mapper fix " Mike Snitzer
2018-10-11 5:40 ` Greg Kroah-Hartman
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=20181010164643.GA10173@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=damien.lemoal@wdc.com \
--cc=dm-devel@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=shhuiw@foxmail.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.