Linux block layer
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, linux-block@vger.kernel.org,
	linux-raid@vger.kernel.org, Alasdair G Kergon <agk@redhat.com>,
	Heinz Mauelshagen <heinzm@redhat.com>,
	Mikulas Patocka <mpatocka@redhat.com>
Subject: [git pull] device mapper fixes for 5.19-rc5
Date: Fri, 1 Jul 2022 12:25:41 -0400	[thread overview]
Message-ID: <Yr8gBVNDik5el/n/@redhat.com> (raw)

Hi Linus,

The following changes since commit 90736eb3232d208ee048493f371075e4272e0944:

  dm mirror log: clear log bits up to BITS_PER_LONG boundary (2022-06-23 14:55:43 -0400)

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-5

for you to fetch changes up to 617b365872a247480e9dcd50a32c8d1806b21861:

  dm raid: fix KASAN warning in raid5_add_disks (2022-06-29 19:48:04 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
- 3 fixes for invalid memory accesses discovered by using KASAN while
  running the lvm2 testsuite's dm-raid tests. Includes changes to MD's
  raid5.c given the dependency dm-raid has on the MD code.

----------------------------------------------------------------
Heinz Mauelshagen (1):
      dm raid: fix accesses beyond end of raid member array

Mikulas Patocka (2):
      dm raid: fix KASAN warning in raid5_remove_disk
      dm raid: fix KASAN warning in raid5_add_disks

 drivers/md/dm-raid.c | 34 ++++++++++++++++++----------------
 drivers/md/raid5.c   |  6 +++++-
 2 files changed, 23 insertions(+), 17 deletions(-)

             reply	other threads:[~2022-07-01 16:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 16:25 Mike Snitzer [this message]
2022-07-01 18:02 ` [git pull] device mapper fixes for 5.19-rc5 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=Yr8gBVNDik5el/n/@redhat.com \
    --to=snitzer@kernel.org \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=heinzm@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-raid@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