linux-kernel - [PATCH 0/1] Signal to disallow open of a dm device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20220704000225.345536-1-dlunev@chromium.org>
Date:   Mon,  4 Jul 2022 10:02:24 +1000
From:   Daniil Lunev <dlunev@...omium.org>
To:     Alasdair Kergon <agk@...hat.com>
Cc:     Brian Geffon <bgeffon@...gle.com>,
        Daniil Lunev <dlunev@...omium.org>,
        Mike Snitzer <snitzer@...nel.org>, dm-devel@...hat.com,
        linux-kernel@...r.kernel.org
Subject: [PATCH 0/1] Signal to disallow open of a dm device

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