From: Mike Snitzer <snitzer@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, linux-block@vger.kernel.org,
Alasdair G Kergon <agk@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
Nathan Huckleberry <nhuck@google.com>
Subject: [git pull] device mapper fixes for 6.0-rc1
Date: Thu, 11 Aug 2022 21:30:44 -0400 [thread overview]
Message-ID: <YvWtRMgKKKSEcEAr@redhat.com> (raw)
Hi Linus,
The following changes since commit 12907efde6ad984f2d76cc1a7dbaae132384d8a5:
dm verity: have verify_wq use WQ_HIGHPRI if "try_verify_in_tasklet" (2022-08-04 15:59:52 -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.0/dm-fixes
for you to fetch changes up to e3a7c2947b9e01b9cedd3f67849c0ae95f0fadfa:
dm bufio: fix some cases where the code sleeps with spinlock held (2022-08-11 11:10:42 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- A few fixes for the DM verity and bufio changes from the 6.0 merge.
- A smatch warning fix for DM writecache locking in writecache_map.
----------------------------------------------------------------
Mike Snitzer (3):
dm bufio: simplify DM_BUFIO_CLIENT_NO_SLEEP locking
dm verity: fix DM_VERITY_OPTS_MAX value yet again
dm verity: fix verity_parse_opt_args parsing
Mikulas Patocka (2):
dm writecache: fix smatch warning about invalid return from writecache_map
dm bufio: fix some cases where the code sleeps with spinlock held
drivers/md/dm-bufio.c | 20 +++++++++++++-------
drivers/md/dm-verity-target.c | 14 ++++++++++++--
drivers/md/dm-writecache.c | 3 ++-
3 files changed, 27 insertions(+), 10 deletions(-)
next reply other threads:[~2022-08-12 1:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 1:30 Mike Snitzer [this message]
2022-08-12 16:02 ` [git pull] device mapper fixes for 6.0-rc1 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=YvWtRMgKKKSEcEAr@redhat.com \
--to=snitzer@kernel.org \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=nhuck@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox