dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: [git pull] device mapper fix for 4.18-rc6
Date: Fri, 20 Jul 2018 18:40:46 -0400	[thread overview]
Message-ID: <20180720224046.GA12929@redhat.com> (raw)
In-Reply-To: <CA+55aFxGp1oh6hYuJVkRKXEaD-F2-qYUYgrerhxqwBTeeAqdxA@mail.gmail.com>

On Fri, Jul 20 2018 at  5:25pm -0400,
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Fri, Jul 20, 2018 at 12:14 PM Mike Snitzer <snitzer@redhat.com> wrote:
> >
> >   Fix DM writecache target to allow an optional offset to the start of
> >   the data and metadata area.  This allows userspace tools (e.g. LVM2)
> >   to place a header and metadata at the front of the writecache device
> >   for its use.
> 
> "fix"?
> 
> Not really.

I hold it to be a "fix" because it was an embarassing oversight on my
part.  Without this, userspace support cannot be properly added.  LVM2
developers raised their inability to put their metadata anywhere and I
was like "oh shit".

Not much point releasing the DM kernel code if it cannot be properly
tied into a volume manager for persistent use across boots, etc.

> But I'm a softie, and I took it. Don't do it again.

Considering dm-writecache was merged for 4.18 I think it important to
get it right.  So thankfully you've chosen wisely ;)

But I certainly sat on this change for a couple rc releases, should've
gotten it to you a couple weeks ago.

Thanks,
Mike

  reply	other threads:[~2018-07-20 22:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20 19:14 [git pull] device mapper fix for 4.18-rc6 Mike Snitzer
2018-07-20 21:25 ` Linus Torvalds
2018-07-20 22:40   ` Mike Snitzer [this message]
2018-07-24 15:18     ` Mikulas Patocka
2018-07-24 15:30       ` David Teigland

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=20180720224046.GA12929@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=mpatocka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).