From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, linux-block@vger.kernel.org,
Alasdair G Kergon <agk@redhat.com>,
Arne Welzel <arne.welzel@corelight.com>,
Changbin Du <changbin.du@gmail.com>,
Mike Snitzer <snitzer@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
Tushar Sugandhi <tusharsu@linux.microsoft.com>
Subject: [git pull] device mapper changes for 5.15
Date: Tue, 31 Aug 2021 12:34:52 -0400 [thread overview]
Message-ID: <YS5aLC4FSqL31PLI@redhat.com> (raw)
Hi Linus,
The following changes since commit 99d26de2f6d79badc80f55b54bd90d4cb9d1ad90:
writeback: make the laptop_mode prototypes available unconditionally (2021-08-10 07:00:50 -0600)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.15/dm-changes
for you to fetch changes up to d3703ef331297b6daa97f5228cbe2a657d0cfd21:
dm crypt: use in_hardirq() instead of deprecated in_irq() (2021-08-20 16:25:07 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Add DM infrastructure for IMA-based remote attestion. These changes
are the basis for deploying DM-based storage in a "cloud" that must
validate configurations end-users run to maintain trust. These DM
changes allow supported DM targets' configurations to be measured
via IMA. But the policy and enforcement (of which configurations are
valid) is managed by something outside the kernel (e.g. Keylime).
- Fix DM crypt scalability regression on systems with many cpus due to
percpu_counter spinlock contention in crypt_page_alloc().
- Use in_hardirq() instead of deprecated in_irq() in DM crypt.
- Add event counters to DM writecache to allow users to further assess
how the writecache is performing.
- Various code cleanup in DM writecache's main IO mapping function.
----------------------------------------------------------------
Arne Welzel (1):
dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc()
Changbin Du (1):
dm crypt: use in_hardirq() instead of deprecated in_irq()
Mike Snitzer (3):
dm writecache: split up writecache_map() to improve code readability
dm writecache: factor out writecache_map_remap_origin()
dm writecache: further writecache_map() cleanup
Mikulas Patocka (2):
dm writecache: report invalid return from writecache_map helpers
dm writecache: add event counters
Tushar Sugandhi (13):
dm ima: measure data on table load
dm ima: measure data on device resume
dm ima: measure data on device remove
dm ima: measure data on table clear
dm ima: measure data on device rename
dm: update target status functions to support IMA measurement
dm: add documentation for IMA measurement support
dm ima: prefix dm table hashes in ima log with hash algorithm
dm ima: add version info to dm related events in ima log
dm ima: prefix ima event name related to device mapper with dm_
dm ima: add a warning in dm_init if duplicate ima events are not measured
dm ima: update dm target attributes for ima measurements
dm ima: update dm documentation for ima measurement support
Documentation/admin-guide/device-mapper/dm-ima.rst | 715 ++++++++++++++++++++
Documentation/admin-guide/device-mapper/index.rst | 1 +
.../admin-guide/device-mapper/writecache.rst | 16 +-
drivers/md/Makefile | 4 +
drivers/md/dm-cache-target.c | 24 +
drivers/md/dm-clone-target.c | 5 +
drivers/md/dm-core.h | 5 +
drivers/md/dm-crypt.c | 38 +-
drivers/md/dm-delay.c | 4 +
drivers/md/dm-dust.c | 4 +
drivers/md/dm-ebs-target.c | 3 +
drivers/md/dm-era-target.c | 4 +
drivers/md/dm-flakey.c | 4 +
drivers/md/dm-ima.c | 750 +++++++++++++++++++++
drivers/md/dm-ima.h | 78 +++
drivers/md/dm-integrity.c | 24 +
drivers/md/dm-ioctl.c | 24 +-
drivers/md/dm-linear.c | 10 +-
drivers/md/dm-log-userspace-base.c | 3 +
drivers/md/dm-log-writes.c | 4 +
drivers/md/dm-log.c | 10 +
drivers/md/dm-mpath.c | 40 +-
drivers/md/dm-ps-historical-service-time.c | 3 +
drivers/md/dm-ps-io-affinity.c | 3 +
drivers/md/dm-ps-queue-length.c | 3 +
drivers/md/dm-ps-round-robin.c | 4 +
drivers/md/dm-ps-service-time.c | 3 +
drivers/md/dm-raid.c | 39 ++
drivers/md/dm-raid1.c | 17 +
drivers/md/dm-snap-persistent.c | 4 +
drivers/md/dm-snap-transient.c | 4 +
drivers/md/dm-snap.c | 13 +
drivers/md/dm-stripe.c | 15 +
drivers/md/dm-switch.c | 4 +
drivers/md/dm-thin.c | 8 +
drivers/md/dm-unstripe.c | 4 +
drivers/md/dm-verity-target.c | 43 ++
drivers/md/dm-writecache.c | 467 ++++++++-----
drivers/md/dm-zoned-target.c | 3 +
drivers/md/dm.c | 12 +-
include/linux/device-mapper.h | 6 +-
include/uapi/linux/dm-ioctl.h | 6 +
security/integrity/ima/ima_main.c | 1 +
43 files changed, 2235 insertions(+), 197 deletions(-)
create mode 100644 Documentation/admin-guide/device-mapper/dm-ima.rst
create mode 100644 drivers/md/dm-ima.c
create mode 100644 drivers/md/dm-ima.h
next reply other threads:[~2021-08-31 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 16:34 Mike Snitzer [this message]
2021-08-31 22:49 ` [git pull] device mapper changes for 5.15 pr-tracker-bot
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=YS5aLC4FSqL31PLI@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=arne.welzel@corelight.com \
--cc=changbin.du@gmail.com \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=tusharsu@linux.microsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox