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>,
Benjamin Marzinski <bmarzins@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>
Subject: [git pull] device mapper fixes for 6.7-rc2
Date: Sat, 18 Nov 2023 11:04:52 -0500 [thread overview]
Message-ID: <ZVjgpLACW4/0NkBB@redhat.com> (raw)
Hi Linus,
The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-6.7/dm-fixes
for you to fetch changes up to 13648e04a9b831b3dfa5cf3887dfa6cf8fe5fe69:
dm-crypt: start allocating with MAX_ORDER (2023-11-17 14:41:15 -0500)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Various fixes for the DM delay target to address regressions
introduced during the 6.7 merge.
- Fixes to both DM bufio and the verity target for no-sleep mode, to
address sleeping while atomic issues.
- Update DM crypt target in response to the treewide change that made
MAX_ORDER inclusive.
-----BEGIN PGP SIGNATURE-----
iQEzBAABCAAdFiEEJfWUX4UqZ4x1O2wixSPxCi2dA1oFAmVY35gACgkQxSPxCi2d
A1pt/gf+NVN/3N0BMYlc/L129+QCIreDH/PuhoxVxMLrhZ8oERw7XkgGIu5JoR1C
Sec5OWJWV0+AZ3kSeW8WBoFFGDdfTYQTId2R3mF3a+34mpAvjTMqnvGkA1GrixCt
xvj2cQjQkBWwwbikAkHZOUoK3UEPFurk/a7oXTAl43kZaV6gWHEAY/bxet9Wuc7+
NWN6xEg7sHhdVgJYltGkOl8Pf9y3zPDUT8SqFT0J7dPEGytNHscozDdRJiLmvoS6
g4WkMkrg87Ude7g0/l7hCM9b3ElamtMsZtyy43cvaKp3UrwFiAzFMCprEl4TS5Br
LNhuwegIBWMVCklRiTDG+uHnbMxKZg==
=9Lfg
-----END PGP SIGNATURE-----
----------------------------------------------------------------
Mikulas Patocka (6):
dm-delay: fix a race between delay_presuspend and delay_bio
dm-delay: fix bugs introduced by kthread mode
dm-delay: avoid duplicate logic
dm-bufio: fix no-sleep mode
dm-verity: don't use blocking calls from tasklets
dm-crypt: start allocating with MAX_ORDER
drivers/md/dm-bufio.c | 87 ++++++++++++++++++++++----------
drivers/md/dm-crypt.c | 2 +-
drivers/md/dm-delay.c | 112 ++++++++++++++++++++----------------------
drivers/md/dm-verity-fec.c | 4 +-
drivers/md/dm-verity-target.c | 23 ++++-----
drivers/md/dm-verity.h | 2 +-
6 files changed, 130 insertions(+), 100 deletions(-)
next reply other threads:[~2023-11-18 16:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 16:04 Mike Snitzer [this message]
2023-11-18 18:33 ` [git pull] device mapper fixes for 6.7-rc2 Linus Torvalds
2023-11-18 19:14 ` Linus Torvalds
2023-11-19 15:21 ` Kirill A. Shutemov
2023-11-20 13:31 ` Kirill A. Shutemov
2023-11-20 17:36 ` Linus Torvalds
2023-11-20 17:40 ` Andrew Morton
2023-11-20 22:17 ` Kirill A. Shutemov
2023-11-21 12:27 ` [PATCH 1/2] mm, treewide: Introduce NR_PAGE_ORDERS Kirill A. Shutemov
2023-11-21 12:27 ` [PATCH 2/2] mm, treewide: Rename MAX_ORDER to MAX_PAGE_ORDER Kirill A. Shutemov
2023-11-21 17:46 ` [PATCH 1/2] mm, treewide: Introduce NR_PAGE_ORDERS Linus Torvalds
2023-11-22 12:34 ` Kirill A. Shutemov
2023-12-05 1:03 ` Kirill A. Shutemov
2023-11-18 18:36 ` [git pull] device mapper fixes for 6.7-rc2 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=ZVjgpLACW4/0NkBB@redhat.com \
--to=snitzer@kernel.org \
--cc=agk@redhat.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--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 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.