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>,
Khazhismel Kumykov <khazhy@google.com>,
Mikulas Patocka <mpatocka@redhat.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: [git pull] device mapper fixes for 5.18-rc3
Date: Fri, 15 Apr 2022 16:43:52 -0400 [thread overview]
Message-ID: <YlnZCHVZNRobAvPZ@redhat.com> (raw)
Hi Linus,
The following changes since commit ce522ba9ef7e2d9fb22a39eb3371c0c64e2a433e:
Linux 5.18-rc2 (2022-04-10 14:21:36 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.18/dm-fixes-2
for you to fetch changes up to 92b914e29af3e99589f2d2876616c0b534892ed4:
dm: fix bio length of empty flush (2022-04-15 16:16:09 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix memory corruption in DM integrity target when tag_size is less
than digest size.
- Fix DM multipath's historical-service-time path selector to not use
sched_clock() and ktime_get_ns(); only use ktime_get_ns().
- Fix dm_io->orig_bio NULL pointer dereference in dm_zone_map_bio()
due to 5.18 changes that overlooked DM zone's use of ->orig_bio
- Fix for regression that broke the use of dm_accept_partial_bio() for
"abnormal" IO (e.g. WRITE ZEROES) that does not need duplicate bios
- Fix DM's issuing of empty flush bio so that it's size is 0.
----------------------------------------------------------------
Khazhismel Kumykov (1):
dm mpath: only use ktime_get_ns() in historical selector
Mike Snitzer (2):
dm zone: fix NULL pointer dereference in dm_zone_map_bio
dm: allow dm_accept_partial_bio() for dm_io without duplicate bios
Mikulas Patocka (1):
dm integrity: fix memory corruption when tag_size is less than digest size
Shin'ichiro Kawasaki (1):
dm: fix bio length of empty flush
drivers/md/dm-integrity.c | 7 +++--
drivers/md/dm-ps-historical-service-time.c | 11 +++----
drivers/md/dm-zone.c | 49 +++++++++++++++++-------------
drivers/md/dm.c | 18 +++++------
4 files changed, 45 insertions(+), 40 deletions(-)
next reply other threads:[~2022-04-15 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 20:43 Mike Snitzer [this message]
2022-04-15 23:04 ` [dm-devel] [git pull] device mapper fixes for 5.18-rc3 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=YlnZCHVZNRobAvPZ@redhat.com \
--to=snitzer@kernel.org \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=khazhy@google.com \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=shinichiro.kawasaki@wdc.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;
as well as URLs for NNTP newsgroup(s).