All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Mike Snitzer <snitzer@redhat.com>
Subject: Re: [git pull] device mapper fix for 4.18-rc6
Date: Tue, 24 Jul 2018 10:30:55 -0500	[thread overview]
Message-ID: <20180724153055.GA12605@redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1807241108340.2382@file01.intranet.prod.int.rdu2.redhat.com>

On Tue, Jul 24, 2018 at 11:18:54AM -0400, Mikulas Patocka wrote:
> > 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".
> 
> This is not oversight.
> 
> It was originally planned that the dm-writecache target would use lvm 
> metadata just like the dm-cache target - if it were implemented this way, 
> no "offset" argument would be needed. But David Teigland who was given the 
> task to implement dm-writecache support in lvm refused to do it this way 
> and he insists that he must put some of his own metadata at the beginning 
> of the cache device before the superblock.
> 
> So this patch is needed because of him.

Mikulas, an offset would have been useful while I was experimenting with
dm-writecache.  I don't actually use or need the offset in lvm.  I don't
think it's a bad idea, but I don't care.

Dave

      reply	other threads:[~2018-07-24 15:30 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
2018-07-24 15:18     ` Mikulas Patocka
2018-07-24 15:30       ` David Teigland [this message]

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=20180724153055.GA12605@redhat.com \
    --to=teigland@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=mpatocka@redhat.com \
    --cc=snitzer@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.