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>,
Benjamin Marzinski <bmarzins@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>
Subject: [git pull] device mapper fixes for 5.19-rc3
Date: Fri, 17 Jun 2022 12:22:54 -0400 [thread overview]
Message-ID: <YqyqXocn0lrLVJ1R@redhat.com> (raw)
Hi Linus,
The following changes since commit b13baccc3850ca8b8cccbf8ed9912dbaa0fdf7f3:
Linux 5.19-rc2 (2022-06-12 16:11:37 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.19/dm-fixes-3
for you to fetch changes up to 85e123c27d5cbc22cfdc01de1e2ca1d9003a02d0:
dm mirror log: round up region bitmap size to BITS_PER_LONG (2022-06-16 19:39:29 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix a race in DM core's dm_start_io_acct that could result in double
accounting for abnormal IO (e.g. discards, write zeroes, etc).
- Fix a use-after-free in DM core's dm_put_live_table_bio.
- Fix a race for REQ_NOWAIT bios being issued despite no support from
underlying DM targets (due to DM table reload at an "unlucky" time)
- Fix access beyond allocated bitmap in DM mirror's log.
----------------------------------------------------------------
Benjamin Marzinski (1):
dm: fix race in dm_start_io_acct
Mikulas Patocka (3):
dm: fix use-after-free in dm_put_live_table_bio
dm: fix narrow race for REQ_NOWAIT bios being issued despite no support
dm mirror log: round up region bitmap size to BITS_PER_LONG
drivers/md/dm-log.c | 3 +--
drivers/md/dm.c | 24 +++++++++++++++++-------
2 files changed, 18 insertions(+), 9 deletions(-)
next reply other threads:[~2022-06-17 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 16:22 Mike Snitzer [this message]
2022-06-17 17:07 ` [git pull] device mapper fixes for 5.19-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=YqyqXocn0lrLVJ1R@redhat.com \
--to=snitzer@kernel.org \
--cc=agk@redhat.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox