All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Wilck <mwilck@suse.com>
To: Demi Marie Obenour <demi@invisiblethingslab.com>,
	Alasdair Kergon <agk@redhat.com>,
	Mike Snitzer <snitzer@kernel.org>,
	dm-devel@lists.linux.dev,  Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	Franck Bui <fbui@suse.com>
Subject: Re: [dm-devel] [PATCH v2 0/4] Diskseq support in device-mapper
Date: Mon, 15 Jan 2024 18:56:16 +0100	[thread overview]
Message-ID: <c09985f5efa9f2351f1ca22cbb286eff2b00d3ad.camel@suse.com> (raw)
In-Reply-To: <20230624230950.2272-1-demi@invisiblethingslab.com>

On Sat, 2023-06-24 at 19:09 -0400, Demi Marie Obenour wrote:
> This work aims to allow userspace to create and destroy device-mapper
> devices in a race-free way.

The discussion about this feature seems to have stalled ... will there
be a v3 of this series any time soon?

Also, I am wondering what should happen if a device-mapper table is
changed in a SUSPEND/LOAD/RESUME cycle. Such operations can change the
content of the device, thus I assume that the diskseq should also
change. But AFAICS this wasn't part of your patch set.

In general, whether the content changes in a reload operation depends
on the target. The multipath target, for example, reloads frequently
without changing the content of the dm device. An ever-changing diskseq
wouldn't make a lot of sense for dm-multipath. But I doubt we want to
start making distinctions on this level, so I guess that diskseq and
multipath just won't go well together.

Regards,
Martin 



  parent reply	other threads:[~2024-01-15 17:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24 23:09 [dm-devel] [PATCH v2 0/4] Diskseq support in device-mapper Demi Marie Obenour
2023-06-24 23:09 ` Demi Marie Obenour
2023-06-24 23:09 ` [dm-devel] [PATCH v2 1/4] dm ioctl: Allow userspace to opt-in to strict parameter checks Demi Marie Obenour
2023-06-24 23:09   ` Demi Marie Obenour
2023-06-24 23:09 ` [dm-devel] [PATCH v2 2/4] dm ioctl: Allow userspace to provide expected diskseq Demi Marie Obenour
2023-06-24 23:09   ` Demi Marie Obenour
2023-06-25 11:23   ` [dm-devel] " Markus Elfring
2023-06-25 17:39     ` Demi Marie Obenour
2023-06-25 17:39       ` Demi Marie Obenour
2023-06-26 12:59       ` [dm-devel] " Dan Carpenter
2023-06-26 12:59         ` Dan Carpenter
2023-06-26 13:30         ` [dm-devel] [v2 " Markus Elfring
2023-06-26 14:51           ` Dan Carpenter
2023-06-26 14:51             ` Dan Carpenter
2023-06-26 15:19             ` [dm-devel] " Markus Elfring
2023-06-26 16:20         ` [dm-devel] [PATCH v2 " Markus Elfring
2023-06-27  6:14           ` Dan Carpenter
2023-06-27  6:14             ` Dan Carpenter
2023-06-27  7:19             ` [dm-devel] [v2 " Markus Elfring
2023-06-24 23:09 ` [dm-devel] [PATCH v2 3/4] dm ioctl: Allow userspace to suppress uevent generation Demi Marie Obenour
2023-06-24 23:09   ` Demi Marie Obenour
2023-06-25 13:25   ` [dm-devel] " Milan Broz
2023-06-25 13:25     ` Milan Broz
2023-06-25 16:02     ` Demi Marie Obenour
2023-06-25 16:02       ` Demi Marie Obenour
2023-06-25 16:33       ` Milan Broz
2023-06-25 16:33         ` Milan Broz
2023-06-25 16:43         ` Demi Marie Obenour
2023-06-25 16:43           ` Demi Marie Obenour
2023-06-25 17:13           ` Milan Broz
2023-06-25 17:13             ` Milan Broz
2023-06-24 23:09 ` [dm-devel] [PATCH v2 4/4] dm ioctl: inform caller about already-existing device Demi Marie Obenour
2023-06-24 23:09   ` Demi Marie Obenour
2024-01-15 17:56 ` Martin Wilck [this message]
2024-01-15 21:44   ` [dm-devel] [PATCH v2 0/4] Diskseq support in device-mapper Demi Marie Obenour
2024-01-16  8:00     ` Martin Wilck

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=c09985f5efa9f2351f1ca22cbb286eff2b00d3ad.camel@suse.com \
    --to=mwilck@suse.com \
    --cc=agk@redhat.com \
    --cc=demi@invisiblethingslab.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=fbui@suse.com \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snitzer@kernel.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.