All of lore.kernel.org
 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,
	Alasdair G Kergon <agk@redhat.com>,
	Mikulas Patocka <mpatocka@redhat.com>,
	Ming Lei <ming.lei@redhat.com>
Subject: [git pull] device mapper fixes for 5.18-rc1
Date: Fri, 1 Apr 2022 15:27:00 -0400	[thread overview]
Message-ID: <YkdSBEf1PpU9w2qs@redhat.com> (raw)

Hi Linus,

The following changes since commit 3f7282139fe1594be464b90141d56738e7a0ea8a:

  Merge tag 'for-5.18/64bit-pi-2022-03-25' of git://git.kernel.dk/linux-block (2022-03-26 12:01:35 -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.18/dm-fixes

for you to fetch changes up to 5291984004edfcc7510024e52eaed044573b79c7:

  dm: fix bio polling to handle possibile BLK_STS_AGAIN (2022-04-01 13:23:12 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
- Fix DM integrity shrink crash due to journal entry not being marked
  unused.

- Fix DM bio polling to handle possibility that underlying device(s)
  return BLK_STS_AGAIN during submission.

- Fix dm_io and dm_target_io flags race condition on Alpha.

- Add some pr_err debugging to help debug cases when DM ioctl
  structure is corrupted.

----------------------------------------------------------------
Mikulas Patocka (3):
      dm ioctl: log an error if the ioctl structure is corrupted
      dm integrity: set journal entry unused when shrinking device
      dm: fix dm_io and dm_target_io flags race condition on Alpha

Ming Lei (1):
      dm: fix bio polling to handle possibile BLK_STS_AGAIN

 drivers/md/dm-core.h      |  4 ++--
 drivers/md/dm-integrity.c |  6 ++++--
 drivers/md/dm-ioctl.c     | 15 ++++++++++++---
 drivers/md/dm.c           | 20 +++++++++++++-------
 include/linux/blk_types.h |  2 ++
 5 files changed, 33 insertions(+), 14 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: Mike Snitzer <snitzer@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com,
	Mikulas Patocka <mpatocka@redhat.com>,
	Alasdair G Kergon <agk@redhat.com>,
	Ming Lei <ming.lei@redhat.com>
Subject: [dm-devel] [git pull] device mapper fixes for 5.18-rc1
Date: Fri, 1 Apr 2022 15:27:00 -0400	[thread overview]
Message-ID: <YkdSBEf1PpU9w2qs@redhat.com> (raw)

Hi Linus,

The following changes since commit 3f7282139fe1594be464b90141d56738e7a0ea8a:

  Merge tag 'for-5.18/64bit-pi-2022-03-25' of git://git.kernel.dk/linux-block (2022-03-26 12:01:35 -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.18/dm-fixes

for you to fetch changes up to 5291984004edfcc7510024e52eaed044573b79c7:

  dm: fix bio polling to handle possibile BLK_STS_AGAIN (2022-04-01 13:23:12 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
- Fix DM integrity shrink crash due to journal entry not being marked
  unused.

- Fix DM bio polling to handle possibility that underlying device(s)
  return BLK_STS_AGAIN during submission.

- Fix dm_io and dm_target_io flags race condition on Alpha.

- Add some pr_err debugging to help debug cases when DM ioctl
  structure is corrupted.

----------------------------------------------------------------
Mikulas Patocka (3):
      dm ioctl: log an error if the ioctl structure is corrupted
      dm integrity: set journal entry unused when shrinking device
      dm: fix dm_io and dm_target_io flags race condition on Alpha

Ming Lei (1):
      dm: fix bio polling to handle possibile BLK_STS_AGAIN

 drivers/md/dm-core.h      |  4 ++--
 drivers/md/dm-integrity.c |  6 ++++--
 drivers/md/dm-ioctl.c     | 15 ++++++++++++---
 drivers/md/dm.c           | 20 +++++++++++++-------
 include/linux/blk_types.h |  2 ++
 5 files changed, 33 insertions(+), 14 deletions(-)

--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel


             reply	other threads:[~2022-04-01 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01 19:27 Mike Snitzer [this message]
2022-04-01 19:27 ` [dm-devel] [git pull] device mapper fixes for 5.18-rc1 Mike Snitzer
2022-04-01 23:43 ` pr-tracker-bot
2022-04-01 23:43   ` 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=YkdSBEf1PpU9w2qs@redhat.com \
    --to=snitzer@kernel.org \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.