From: Mike Snitzer <snitzer@redhat.com>
To: "Paul B. Henson" <henson@acm.org>
Cc: 'device-mapper development' <dm-devel@redhat.com>
Subject: Re: dm-cache questions
Date: Fri, 13 Dec 2013 16:21:56 -0500 [thread overview]
Message-ID: <20131213212156.GB11452@redhat.com> (raw)
In-Reply-To: <0e4a01cef83b$c9afe5b0$5d0fb110$@acm.org>
On Fri, Dec 13 2013 at 2:44pm -0500,
Paul B. Henson <henson@acm.org> wrote:
> > From: Mike Snitzer
> > Sent: Friday, December 13, 2013 6:20 AM
> >
> > But in general it is the task of other distro vendors to backport stable
> > fixes to their products.
>
> Got it, thanks. I see the recent beta announcement officially confirmed that
> RHEL 7 will be based on 3.10, so I'm guessing somebody in your organization
> is going to be back porting to that stable release at least :). Although I
> suppose that could be in your internal wad-o-patches rather than official
> upstream commits.
All the latest dm-cache changes will be included in RHEL7. I'm the
lucky guy who brings these changes back.
FYI, the most recent dm-cache fixes should hopefully be available in
linus's tree shortly. Joe fixed the dm cache metadata leak that he
advised you to wait for before using dm-cache in a more serious way.
See:
http://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/log/?h=for-linus
next prev parent reply other threads:[~2013-12-13 21:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 1:56 dm-cache questions Paul B. Henson
2013-12-10 9:50 ` Joe Thornber
2013-12-10 21:04 ` Paul B. Henson
2013-12-11 1:03 ` Alasdair G Kergon
2013-12-11 2:08 ` Paul B. Henson
2013-12-11 15:06 ` Mike Snitzer
2013-12-12 2:14 ` Paul B. Henson
2013-12-13 14:20 ` Mike Snitzer
2013-12-13 19:44 ` Paul B. Henson
2013-12-13 21:21 ` Mike Snitzer [this message]
2013-12-14 0:59 ` Paul B. Henson
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=20131213212156.GB11452@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=henson@acm.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.