All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniil Lunev <dlunev@chromium.org>
To: Alasdair Kergon <agk@redhat.com>
Cc: Brian Geffon <bgeffon@google.com>,
	Daniil Lunev <dlunev@chromium.org>,
	Mike Snitzer <snitzer@kernel.org>,
	dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] Signal to disallow open of a dm device
Date: Mon,  4 Jul 2022 10:02:24 +1000	[thread overview]
Message-ID: <20220704000225.345536-1-dlunev@chromium.org> (raw)

There was a previuous discussion upstream about this kind of
functionality (see https://lkml.org/lkml/2022/1/24/633). The previous
patchset was rejected with concerns about how the feature was
integrated. This patch takes a different approach, and instead of
tying itself to unrelated mechanisms (e.g. deffer remove), this one
allows an explicit signal via message interface to signalize device
mapper shall block any further access to the device. The primary use
case is to restrict userspace access to decrypted data after a device
was setup with a kernel facility (e.g. swap).


Daniil Lunev (1):
  dm: add message command to disallow device open

 drivers/md/dm-core.h          |  1 +
 drivers/md/dm-ioctl.c         | 10 ++++++++++
 drivers/md/dm.c               | 12 ++++++++++++
 drivers/md/dm.h               | 10 ++++++++++
 include/uapi/linux/dm-ioctl.h |  5 +++++
 5 files changed, 38 insertions(+)

-- 
2.31.0


WARNING: multiple messages have this Message-ID (diff)
From: Daniil Lunev <dlunev@chromium.org>
To: Alasdair Kergon <agk@redhat.com>
Cc: dm-devel@redhat.com, Daniil Lunev <dlunev@chromium.org>,
	Mike Snitzer <snitzer@kernel.org>,
	Brian Geffon <bgeffon@google.com>,
	linux-kernel@vger.kernel.org
Subject: [dm-devel] [PATCH 0/1] Signal to disallow open of a dm device
Date: Mon,  4 Jul 2022 10:02:24 +1000	[thread overview]
Message-ID: <20220704000225.345536-1-dlunev@chromium.org> (raw)

There was a previuous discussion upstream about this kind of
functionality (see https://lkml.org/lkml/2022/1/24/633). The previous
patchset was rejected with concerns about how the feature was
integrated. This patch takes a different approach, and instead of
tying itself to unrelated mechanisms (e.g. deffer remove), this one
allows an explicit signal via message interface to signalize device
mapper shall block any further access to the device. The primary use
case is to restrict userspace access to decrypted data after a device
was setup with a kernel facility (e.g. swap).


Daniil Lunev (1):
  dm: add message command to disallow device open

 drivers/md/dm-core.h          |  1 +
 drivers/md/dm-ioctl.c         | 10 ++++++++++
 drivers/md/dm.c               | 12 ++++++++++++
 drivers/md/dm.h               | 10 ++++++++++
 include/uapi/linux/dm-ioctl.h |  5 +++++
 5 files changed, 38 insertions(+)

-- 
2.31.0

--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel


             reply	other threads:[~2022-07-04  0:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04  0:02 Daniil Lunev [this message]
2022-07-04  0:02 ` [dm-devel] [PATCH 0/1] Signal to disallow open of a dm device Daniil Lunev
2022-07-04  0:02 ` [PATCH 1/1] dm: add message command to disallow device open Daniil Lunev
2022-07-04  0:02   ` [dm-devel] " Daniil Lunev
2022-07-14 20:13   ` Mike Snitzer
2022-07-14 20:13     ` [dm-devel] " Mike Snitzer
2022-07-14 23:42     ` Daniil Lunev
2022-07-14 23:42       ` [dm-devel] " Daniil Lunev
2022-07-15  9:36       ` Mikulas Patocka
2022-07-15  9:36         ` Mikulas Patocka
2022-07-15 19:38         ` Zdenek Kabelac
2022-07-15 19:38           ` Zdenek Kabelac
2022-07-18 23:42           ` Daniil Lunev
2022-07-18 23:42             ` Daniil Lunev
2022-08-03  4:12             ` Daniil Lunev
2022-08-03  4:12               ` Daniil Lunev
2022-08-03  4:23               ` Eric Biggers
2022-08-03  4:23                 ` Eric Biggers
2022-08-03  4:29                 ` Daniil Lunev
2022-08-03  4:29                   ` Daniil Lunev
2022-08-03 16:30                   ` Mike Snitzer
2022-08-03 16:30                     ` Mike Snitzer
2022-08-03 20:49                     ` Daniil Lunev
2022-08-03 20:49                       ` [dm-devel] " Daniil Lunev
2022-08-03 18:25                   ` Eric Biggers
2022-08-03 18:25                     ` Eric Biggers
2022-08-03 20:44                     ` Daniil Lunev
2022-08-03 20:44                       ` Daniil Lunev
2022-08-03 21:49                       ` Eric Biggers
2022-08-03 21:49                         ` Eric Biggers
2022-08-03 23:38                         ` Daniil Lunev
2022-08-03 23:38                           ` Daniil Lunev

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=20220704000225.345536-1-dlunev@chromium.org \
    --to=dlunev@chromium.org \
    --cc=agk@redhat.com \
    --cc=bgeffon@google.com \
    --cc=dm-devel@redhat.com \
    --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.