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>,
"Cai Huoqing" <caihuoqing@baidu.com>,
"Christoph Hellwig" <hch@lst.de>,
"Christophe JAILLET" <christophe.jaillet@wanadoo.fr>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Michael Weiß" <michael.weiss@aisec.fraunhofer.de>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Subject: [git pull] device mapper changes for 5.16
Date: Mon, 8 Nov 2021 16:25:28 -0500 [thread overview]
Message-ID: <YYmVyArwFwN/FdfA@redhat.com> (raw)
Hi Linus,
The following changes since commit d208b89401e073de986dc891037c5a668f5d5d95:
dm: fix mempool NULL pointer race when completing IO (2021-10-12 13:54:10 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.16/dm-changes
for you to fetch changes up to 7552750d0494fdd12f71acd8a432f51334a4462d:
dm table: log table creation error code (2021-11-01 13:28:52 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Add DM core support for emitting audit events through the audit
subsystem. Also enhance both the integrity and crypt targets to emit
events to via dm-audit.
- Various other simple code improvements and cleanups.
----------------------------------------------------------------
Cai Huoqing (2):
dm crypt: Make use of the helper macro kthread_run()
dm writecache: Make use of the helper macro kthread_run()
Christoph Hellwig (4):
dm integrity: use bvec_kmap_local in integrity_metadata
dm integrity: use bvec_kmap_local in __journal_read_write
dm log writes: use memcpy_from_bvec in log_writes_map
dm verity: use bvec_kmap_local in verity_for_bv_block
Christophe JAILLET (1):
dm: Remove redundant flush_workqueue() calls
Luis Chamberlain (1):
dm: add add_disk() error handling
Michael Weiß (3):
dm: introduce audit event module for device mapper
dm integrity: log audit events for dm-integrity target
dm crypt: log aead integrity violations to audit subsystem
Michał Mirosław (2):
dm: make workqueue names device-specific
dm table: log table creation error code
drivers/md/Kconfig | 10 ++++++
drivers/md/Makefile | 4 +++
drivers/md/dm-audit.c | 84 +++++++++++++++++++++++++++++++++++++++++++
drivers/md/dm-audit.h | 66 ++++++++++++++++++++++++++++++++++
drivers/md/dm-bufio.c | 1 -
drivers/md/dm-crypt.c | 25 +++++++++----
drivers/md/dm-integrity.c | 35 +++++++++++++-----
drivers/md/dm-log-writes.c | 6 ++--
drivers/md/dm-table.c | 4 +--
drivers/md/dm-verity-target.c | 6 ++--
drivers/md/dm-writecache.c | 6 ++--
drivers/md/dm-zoned-target.c | 1 -
drivers/md/dm.c | 6 ++--
include/uapi/linux/audit.h | 2 ++
14 files changed, 224 insertions(+), 32 deletions(-)
create mode 100644 drivers/md/dm-audit.c
create mode 100644 drivers/md/dm-audit.h
next reply other threads:[~2021-11-08 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 21:25 Mike Snitzer [this message]
2021-11-09 19:31 ` [dm-devel] [git pull] device mapper changes for 5.16 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=YYmVyArwFwN/FdfA@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=caihuoqing@baidu.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=michael.weiss@aisec.fraunhofer.de \
--cc=mirq-linux@rere.qmqm.pl \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).