Linux-Block Archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@lists.linux.dev, linux-block@vger.kernel.org,
	Alasdair G Kergon <agk@redhat.com>,
	Mikulas Patocka <mpatocka@redhat.com>,
	Benjamin Marzinski <bmarzins@redhat.com>,
	Christoph Hellwig <hch@lst.de>,
	Joel Colledge <joel.colledge@linbit.com>,
	yangerkun <yangerkun@huawei.com>
Subject: [git pull] device mapper changes for 6.10
Date: Tue, 14 May 2024 12:08:19 -0400	[thread overview]
Message-ID: <ZkOMczEgGuPBOCrr@redhat.com> (raw)

Hi Linus,

The following changes since commit 48ef0ba12e6b77a1ce5d09c580c38855b090ae7c:

  dm: restore synchronous close of device mapper block device (2024-04-16 11:32:07 -0400)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-6.10/dm-changes

for you to fetch changes up to 8b21ac87d550acc4f6207764fed0cf6f0e3966cd:

  dm-delay: remove timer_lock (2024-05-09 09:10:58 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
- Add a dm-crypt optional "high_priority" flag that enables the crypt
  workqueues to use WQ_HIGHPRI.

- Export dm-crypt workqueues via sysfs (by enabling WQ_SYSFS) to allow
  for improved visibility and controls over IO and crypt workqueues.

- Fix dm-crypt to no longer constrain max_segment_size to PAGE_SIZE.
  This limit isn't needed given that the block core provides late bio
  splitting if bio exceeds underlying limits (e.g. max_segment_size).

- Fix dm-crypt crypt_queue's use of WQ_UNBOUND to not use
  WQ_CPU_INTENSIVE because it is meaningless with WQ_UNBOUND.

- Fix various issues with dm-delay target (ranging from a resource
  teardown fix, a fix for hung task when using kthread mode, and other
  improvements that followed from code inspection).
-----BEGIN PGP SIGNATURE-----

iQEzBAABCAAdFiEEJfWUX4UqZ4x1O2wixSPxCi2dA1oFAmZDiggACgkQxSPxCi2d
A1oQrwf7BUHy7ehwCjRrVlFTteIlx0ULTpPxictakN/S+xZfcZUcbE20OjNVzdk9
m5dx4Gn557rlMkiC4NDlHazVEVM5BbTpih27rvUgvX2nchUUdfHIT1OvU0isT4Yi
h9g/o7i9DnBPjvyNjpXjP9YE7Xg8u2X9mxpv8DyU5M+QpFuofwzsfkCP7g14B0g2
btGxT3AZ5Bo8A/csKeSqHq13Nbq/dcAZZ3IvjIg1xSXjm6CoQ04rfO0TN6SKfsFJ
GXteBS2JT1MMcXf3oKweAeQduTE+psVFea7gt/8haKFldnV+DpPNg1gU/7rza5Os
eL1+L1iPY5fuEJIkaqPjBVRGkxQqHg==
=+OhH
-----END PGP SIGNATURE-----

----------------------------------------------------------------
Benjamin Marzinski (4):
      dm-delay: fix workqueue delay_timer race
      dm-delay: fix max_delay calculations
      dm-delay: change locking to avoid contention
      dm-delay: remove timer_lock

Christoph Hellwig (1):
      dm: use queue_limits_set

Joel Colledge (1):
      dm-delay: fix hung task introduced by kthread mode

Mike Snitzer (2):
      dm-crypt: stop constraining max_segment_size to PAGE_SIZE
      dm-crypt: don't set WQ_CPU_INTENSIVE for WQ_UNBOUND crypt_queue

Mikulas Patocka (1):
      dm-crypt: add the optional "high_priority" flag

yangerkun (1):
      dm-crypt: export sysfs of all workqueues

 .../admin-guide/device-mapper/dm-crypt.rst         |  5 ++
 drivers/md/dm-crypt.c                              | 73 +++++++++++++++-------
 drivers/md/dm-delay.c                              | 60 +++++++++---------
 drivers/md/dm-table.c                              | 27 ++++----
 4 files changed, 97 insertions(+), 68 deletions(-)

             reply	other threads:[~2024-05-14 16:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 16:08 Mike Snitzer [this message]
2024-05-15  1:49 ` [git pull] device mapper changes for 6.10 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=ZkOMczEgGuPBOCrr@redhat.com \
    --to=snitzer@kernel.org \
    --cc=agk@redhat.com \
    --cc=bmarzins@redhat.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=hch@lst.de \
    --cc=joel.colledge@linbit.com \
    --cc=linux-block@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=yangerkun@huawei.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).