All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-block@vger.kernel.org,
	Mikulas Patocka <mpatocka@redhat.com>,
	dm-devel@redhat.com, John Keeping <john@metanate.com>,
	Alasdair G Kergon <agk@redhat.com>
Subject: [dm-devel] [git pull] device mapper fixes for 5.13-rc4
Date: Thu, 27 May 2021 14:52:25 -0400	[thread overview]
Message-ID: <YK/qaSCdhqDlKh1l@redhat.com> (raw)

Hi Linus,

The following changes since commit c4681547bcce777daf576925a966ffa824edd09d:

  Linux 5.13-rc3 (2021-05-23 11:42:48 -1000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.13/dm-fixes-2

for you to fetch changes up to 7e768532b2396bcb7fbf6f82384b85c0f1d2f197:

  dm snapshot: properly fix a crash when an origin has no snapshots (2021-05-25 16:19:58 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
- Fix DM verity target's 'require_signatures' module_param permissions.

- Revert DM snapshot fix from v5.13-rc3 and then properly fix crash
  when an origin has no snapshots. This allows only the proper fix to
  go to stable@ (since the original fix was successfully dropped).

----------------------------------------------------------------
John Keeping (1):
      dm verity: fix require_signatures module_param permissions

Mikulas Patocka (2):
      dm snapshot: revert "fix a crash when an origin has no snapshots"
      dm snapshot: properly fix a crash when an origin has no snapshots

 drivers/md/dm-snap.c              | 3 ++-
 drivers/md/dm-verity-verify-sig.c | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

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


WARNING: multiple messages have this Message-ID (diff)
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>,
	John Keeping <john@metanate.com>,
	Mikulas Patocka <mpatocka@redhat.com>
Subject: [git pull] device mapper fixes for 5.13-rc4
Date: Thu, 27 May 2021 14:52:25 -0400	[thread overview]
Message-ID: <YK/qaSCdhqDlKh1l@redhat.com> (raw)

Hi Linus,

The following changes since commit c4681547bcce777daf576925a966ffa824edd09d:

  Linux 5.13-rc3 (2021-05-23 11:42:48 -1000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.13/dm-fixes-2

for you to fetch changes up to 7e768532b2396bcb7fbf6f82384b85c0f1d2f197:

  dm snapshot: properly fix a crash when an origin has no snapshots (2021-05-25 16:19:58 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
- Fix DM verity target's 'require_signatures' module_param permissions.

- Revert DM snapshot fix from v5.13-rc3 and then properly fix crash
  when an origin has no snapshots. This allows only the proper fix to
  go to stable@ (since the original fix was successfully dropped).

----------------------------------------------------------------
John Keeping (1):
      dm verity: fix require_signatures module_param permissions

Mikulas Patocka (2):
      dm snapshot: revert "fix a crash when an origin has no snapshots"
      dm snapshot: properly fix a crash when an origin has no snapshots

 drivers/md/dm-snap.c              | 3 ++-
 drivers/md/dm-verity-verify-sig.c | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

             reply	other threads:[~2021-05-27 18:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 18:52 Mike Snitzer [this message]
2021-05-27 18:52 ` [git pull] device mapper fixes for 5.13-rc4 Mike Snitzer
2021-05-27 22:04 ` [dm-devel] " pr-tracker-bot
2021-05-27 22:04   ` 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=YK/qaSCdhqDlKh1l@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=john@metanate.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 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.