From: Christoph Hellwig <hch@infradead.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Mike Snitzer <msnitzer@redhat.com>,
Zdenek Kabelac <zkabelac@redhat.com>,
lvm-devel@redhat.com, dm-devel@redhat.com,
Milan Broz <mbroz@redhat.com>
Subject: Re: [PATCH] dm: introduce DM_GET_TARGET_VERSION
Date: Mon, 16 Sep 2019 11:01:07 -0700 [thread overview]
Message-ID: <20190916180107.GA725@infradead.org> (raw)
In-Reply-To: <alpine.LRH.2.02.1909160553360.11421@file01.intranet.prod.int.rdu2.redhat.com>
On Mon, Sep 16, 2019 at 05:55:42AM -0400, Mikulas Patocka wrote:
> This patch introduces a new ioctl DM_GET_TARGET_VERSION. It will load a
> target that is specified in the "name" entry in the parameter structure
> and return its version.
>
> This functionality is intended to be used by cryptsetup, so that it can
> query kernel capabilities before activating the device.
Well, if you want to query kernel features you better ask for a feature
bitmap than a version number, which can be rather meaningless with
the amount of backporting that is going on.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: lvm-devel@redhat.com
Subject: [dm-devel] [PATCH] dm: introduce DM_GET_TARGET_VERSION
Date: Mon, 16 Sep 2019 11:01:07 -0700 [thread overview]
Message-ID: <20190916180107.GA725@infradead.org> (raw)
In-Reply-To: <alpine.LRH.2.02.1909160553360.11421@file01.intranet.prod.int.rdu2.redhat.com>
On Mon, Sep 16, 2019 at 05:55:42AM -0400, Mikulas Patocka wrote:
> This patch introduces a new ioctl DM_GET_TARGET_VERSION. It will load a
> target that is specified in the "name" entry in the parameter structure
> and return its version.
>
> This functionality is intended to be used by cryptsetup, so that it can
> query kernel capabilities before activating the device.
Well, if you want to query kernel features you better ask for a feature
bitmap than a version number, which can be rather meaningless with
the amount of backporting that is going on.
next prev parent reply other threads:[~2019-09-16 18:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 9:55 [PATCH] dm: introduce DM_GET_TARGET_VERSION Mikulas Patocka
2019-09-16 9:55 ` Mikulas Patocka
2019-09-16 9:58 ` [PATCH] lvm: " Mikulas Patocka
2019-09-16 9:58 ` Mikulas Patocka
2019-09-16 14:21 ` dm: " Mike Snitzer
2019-09-16 14:21 ` Mike Snitzer
2019-09-16 18:01 ` Christoph Hellwig [this message]
2019-09-16 18:01 ` [dm-devel] [PATCH] " Christoph Hellwig
2019-09-16 18:16 ` Milan Broz
2019-09-16 18:16 ` [dm-devel] " Milan Broz
2019-09-17 6:32 ` Christoph Hellwig
2019-09-17 6:32 ` [dm-devel] " Christoph Hellwig
2019-09-17 13:39 ` Mike Snitzer
2019-09-17 13:39 ` Mike Snitzer
2019-09-17 13:56 ` [PATCH] " John Dorminy
2019-09-17 13:56 ` [dm-devel] " John Dorminy
2019-09-17 14:06 ` Mike Snitzer
2019-09-17 14:06 ` Mike Snitzer
2019-09-17 15:38 ` Mikulas Patocka
2019-09-17 15:38 ` Mikulas Patocka
2019-09-17 15:44 ` John Dorminy
2019-09-17 15:44 ` John Dorminy
2019-09-17 20:08 ` Mike Snitzer
2019-09-17 20:08 ` Mike Snitzer
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=20190916180107.GA725@infradead.org \
--to=hch@infradead.org \
--cc=dm-devel@redhat.com \
--cc=lvm-devel@redhat.com \
--cc=mbroz@redhat.com \
--cc=mpatocka@redhat.com \
--cc=msnitzer@redhat.com \
--cc=zkabelac@redhat.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.