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>,
Mikulas Patocka <mpatocka@redhat.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Sergei Shtepa <sergei.shtepa@veeam.com>,
Thomas Gleixner <tglx@linutronix.de>,
axboe@kernel.dk, vgoyal@redhat.com
Subject: [git pull] device mapper fixes for 5.10-rc7
Date: Fri, 4 Dec 2020 16:05:21 -0500 [thread overview]
Message-ID: <20201204210521.GA3937@redhat.com> (raw)
Hi Linus,
The following changes since commit 09162bc32c880a791c6c0668ce0745cf7958f576:
Linux 5.10-rc4 (2020-11-15 16:44:31 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.10/dm-fixes
for you to fetch changes up to bde3808bc8c2741ad3d804f84720409aee0c2972:
dm: remove invalid sparse __acquires and __releases annotations (2020-12-04 15:25:18 -0500)
Please pull, thanks!
Mike
----------------------------------------------------------------
- Fix DM's bio splitting changes that were made during v5.9.
Restores splitting in terms of varied per-target ti->max_io_len
rather than use block core's single stacked 'chunk_sectors' limit.
- Like DM crypt, update DM integrity to not use crypto drivers that
have CRYPTO_ALG_ALLOCATES_MEMORY set.
- Fix DM writecache target's argument parsing and status display.
- Remove needless BUG() from dm writecache's persistent_memory_claim()
- Remove old gcc workaround in DM cache target's block_div() for ARM
link errors now that gcc >= 4.9 is required.
- Fix RCU locking in dm_blk_report_zones and dm_dax_zero_page_range.
- Remove old, and now frowned upon, BUG_ON(in_interrupt()) in
dm_table_event().
- Remove invalid sparse annotations from dm_prepare_ioctl() and
dm_unprepare_ioctl().
----------------------------------------------------------------
Mike Snitzer (4):
dm writecache: remove BUG() and fail gracefully instead
dm: fix IO splitting
dm: fix double RCU unlock in dm_dax_zero_page_range() error path
dm: remove invalid sparse __acquires and __releases annotations
Mikulas Patocka (3):
dm integrity: don't use drivers that have CRYPTO_ALG_ALLOCATES_MEMORY
dm writecache: advance the number of arguments when reporting max_age
dm writecache: fix the maximum number of arguments
Nick Desaulniers (1):
Revert "dm cache: fix arm link errors with inline"
Sergei Shtepa (1):
dm: fix bug with RCU locking in dm_blk_report_zones
Thomas Gleixner (1):
dm table: Remove BUG_ON(in_interrupt())
block/blk-merge.c | 2 +-
drivers/md/dm-cache-target.c | 4 ----
drivers/md/dm-integrity.c | 4 ++--
drivers/md/dm-table.c | 11 -----------
drivers/md/dm-writecache.c | 6 ++++--
drivers/md/dm.c | 29 +++++++++++++++--------------
include/linux/blkdev.h | 11 ++++++-----
7 files changed, 28 insertions(+), 39 deletions(-)
next reply other threads:[~2020-12-04 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 21:05 Mike Snitzer [this message]
2020-12-04 21:35 ` [git pull] device mapper fixes for 5.10-rc7 pr-tracker-bot
2020-12-04 22:37 ` [PATCH] block: fix incorrect branching in blk_max_size_offset() [was: Re: [git pull] device mapper fixes for 5.10-rc7] Mike Snitzer
2020-12-04 23:12 ` [git pull] device mapper induced block fix for 5.10-rc7 Mike Snitzer
2020-12-05 19:21 ` [dm-devel] " 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=20201204210521.GA3937@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=ndesaulniers@google.com \
--cc=sergei.shtepa@veeam.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vgoyal@redhat.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