public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
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>, Joe Thornber <ejt@redhat.com>
Subject: [git pull] device mapper fixes for 5.16-rc6
Date: Thu, 16 Dec 2021 12:49:16 -0500	[thread overview]
Message-ID: <Ybt8HMQUZn7mlvTG@redhat.com> (raw)

Hi Linus,

The following changes since commit 136057256686de39cc3a07c2e39ef6bc43003ff6:

  Linux 5.16-rc2 (2021-11-21 13:47:39 -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.16/dm-fixes

for you to fetch changes up to 1cef171abd39102dcc862c6bfbf7f954f4f1f66f:

  dm integrity: fix data corruption due to improper use of bvec_kmap_local (2021-12-15 14:16:35 -0500)

Please pull, thanks.
Mike

----------------------------------------------------------------
- Fix use after free in DM btree remove's rebalance_children().

- Fix DM integrity data corruption, introduced during 5.16 merge, due
  to improper use of bvec_kmap_local().

----------------------------------------------------------------
Joe Thornber (1):
      dm btree remove: fix use after free in rebalance_children()

Mike Snitzer (1):
      dm integrity: fix data corruption due to improper use of bvec_kmap_local

 drivers/md/dm-integrity.c                    | 2 +-
 drivers/md/persistent-data/dm-btree-remove.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)


             reply	other threads:[~2021-12-16 17:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 17:49 Mike Snitzer [this message]
2021-12-16 18:43 ` [git pull] device mapper fixes for 5.16-rc6 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=Ybt8HMQUZn7mlvTG@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ejt@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --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