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>,
	Damien Le Moal <damien.lemoal@wdc.com>,
	Mikulas Patocka <mpatocka@redhat.com>,
	Ye Bin <yebin10@huawei.com>
Subject: [git pull] device mapper fixes for 5.9-rc4
Date: Wed, 2 Sep 2020 14:02:48 -0400	[thread overview]
Message-ID: <20200902180248.GA32957@lobo> (raw)

Hi Linus,

The following changes since commit f75aef392f869018f78cfedf3c320a6b3fcfda6b:

  Linux 5.9-rc3 (2020-08-30 16:01:54 -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.9/dm-fixes

for you to fetch changes up to 3a653b205f29b3f9827a01a0c88bfbcb0d169494:

  dm thin metadata: Fix use-after-free in dm_bm_set_read_only (2020-09-02 13:38:40 -0400)

Please pull, thanks!
Mike

----------------------------------------------------------------
- DM writecache fix to allow dax_direct_access() to partitioned pmem
  devices.

- DM multipath fix to avoid any Path Group initialization if
  'pg_init_in_progress' isn't set.

- DM crypt fix to use DECLARE_CRYPTO_WAIT() for onstack wait
  structures.

- DM integrity fix to properly check integrity after device creation
  when in bitmap mode.

- DM thinp and cache target __create_persistent_data_objects() fixes
  to reset the metadata's dm_block_manager pointer from PTR_ERR to
  NULL before returning from error path.

- DM persistent-data block manager fix to guard against
  dm_block_manager NULL pointer dereference in dm_bm_is_read_only()
  and update various opencoded bm->read_only checks to use
  dm_bm_is_read_only() instead.

----------------------------------------------------------------
Damien Le Moal (1):
      dm crypt: Initialize crypto wait structures

Mike Snitzer (1):
      dm mpath: fix racey management of PG initialization

Mikulas Patocka (2):
      dm writecache: handle DAX to partitions on persistent memory correctly
      dm integrity: fix error reporting in bitmap mode after creation

Ye Bin (3):
      dm cache metadata: Avoid returning cmd->bm wild pointer on error
      dm thin metadata:  Avoid returning cmd->bm wild pointer on error
      dm thin metadata: Fix use-after-free in dm_bm_set_read_only

 drivers/md/dm-cache-metadata.c                |  8 ++++++--
 drivers/md/dm-crypt.c                         |  4 ++--
 drivers/md/dm-integrity.c                     | 12 ++++++++++++
 drivers/md/dm-mpath.c                         | 22 +++++++++++++++-------
 drivers/md/dm-thin-metadata.c                 | 10 +++++++---
 drivers/md/dm-writecache.c                    | 12 ++++++++++--
 drivers/md/persistent-data/dm-block-manager.c | 14 ++++++++------
 7 files changed, 60 insertions(+), 22 deletions(-)

             reply	other threads:[~2020-09-02 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02 18:02 Mike Snitzer [this message]
2020-09-02 20:08 ` [git pull] device mapper fixes for 5.9-rc4 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=20200902180248.GA32957@lobo \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=damien.lemoal@wdc.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=yebin10@huawei.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