linux-block.vger.kernel.org archive mirror
 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>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Joe Thornber <ejt@redhat.com>, Kees Cook <keescook@chromium.org>
Subject: [git pull] device mapper changes for 5.17
Date: Wed, 12 Jan 2022 11:24:29 -0500	[thread overview]
Message-ID: <Yd8AveH8D+Nk2ILp@redhat.com> (raw)

Hi Linus,

The following changes since commit fc74e0a40e4f9fd0468e34045b0c45bba11dcbb2:

  Linux 5.16-rc7 (2021-12-26 13:17:17 -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.17/dm-changes

for you to fetch changes up to eaac0b590a47c717ef36cbfd1c528cd154c965a1:

  dm sysfs: use default_groups in kobj_type (2022-01-06 09:48:55 -0500)

Please pull, thanks.
Mike

----------------------------------------------------------------
- Fixes and improvements to dm btree and dm space map code in
  persistent-data library used by thinp and cache.

- Update DM integrity to use struct_group() to zero struct
  journal_sector.

- Update DM sysfs to use default_groups in kobj_type.

----------------------------------------------------------------
Greg Kroah-Hartman (1):
      dm sysfs: use default_groups in kobj_type

Joe Thornber (5):
      dm btree spine: remove extra node_check function declaration
      dm btree spine: eliminate duplicate le32_to_cpu() in node_check()
      dm btree remove: change a bunch of BUG_ON() calls to proper errors
      dm btree: add a defensive bounds check to insert_at()
      dm space map common: add bounds check to sm_ll_lookup_bitmap()

Kees Cook (1):
      dm integrity: Use struct_group() to zero struct journal_sector

 drivers/md/dm-integrity.c                        |   9 +-
 drivers/md/dm-sysfs.c                            |   3 +-
 drivers/md/persistent-data/dm-btree-remove.c     | 173 ++++++++++++++++-------
 drivers/md/persistent-data/dm-btree-spine.c      |  12 +-
 drivers/md/persistent-data/dm-btree.c            |   8 +-
 drivers/md/persistent-data/dm-space-map-common.c |   5 +
 6 files changed, 145 insertions(+), 65 deletions(-)


             reply	other threads:[~2022-01-12 16:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 16:24 Mike Snitzer [this message]
2022-01-12 19:12 ` [git pull] device mapper changes for 5.17 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=Yd8AveH8D+Nk2ILp@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ejt@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=keescook@chromium.org \
    --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;
as well as URLs for NNTP newsgroup(s).