From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: JeongHyeon Lee <jhs2.lee@samsung.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Mikulas Patocka <mpatocka@redhat.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Alasdair G Kergon <agk@redhat.com>
Subject: [dm-devel] [git pull] device mapper fixes for 5.12-rc5
Date: Fri, 26 Mar 2021 15:19:50 -0400 [thread overview]
Message-ID: <20210326191949.GA24195@redhat.com> (raw)
Hi Linus,
The following changes since commit 0d02ec6b3136c73c09e7859f0d0e4e2c4c07b49b:
Linux 5.12-rc4 (2021-03-21 14:56:43 -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.12/dm-fixes-2
for you to fetch changes up to 4edbe1d7bcffcd6269f3b5eb63f710393ff2ec7a:
dm ioctl: fix out of bounds array access when no devices (2021-03-26 14:51:50 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix DM verity target's optional argument processing.
- Fix DM core's zoned model and zone sectors checks.
- Fix spurious "detected capacity change" pr_info() when creating new
DM device.
- Fix DM ioctl out of bounds array access in handling of
DM_LIST_DEVICES_CMD when no devices exist.
----------------------------------------------------------------
JeongHyeon Lee (1):
dm verity: fix DM_VERITY_OPTS_MAX value
Mikulas Patocka (2):
dm: don't report "detected capacity change" on device creation
dm ioctl: fix out of bounds array access when no devices
Shin'ichiro Kawasaki (1):
dm table: Fix zoned model check and zone sectors check
drivers/md/dm-ioctl.c | 2 +-
drivers/md/dm-table.c | 33 +++++++++++++++++++++++++--------
drivers/md/dm-verity-target.c | 2 +-
drivers/md/dm-zoned-target.c | 2 +-
drivers/md/dm.c | 5 ++++-
include/linux/device-mapper.h | 15 ++++++++++++++-
6 files changed, 46 insertions(+), 13 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>,
JeongHyeon Lee <jhs2.lee@samsung.com>,
Mikulas Patocka <mpatocka@redhat.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: [git pull] device mapper fixes for 5.12-rc5
Date: Fri, 26 Mar 2021 15:19:50 -0400 [thread overview]
Message-ID: <20210326191949.GA24195@redhat.com> (raw)
Hi Linus,
The following changes since commit 0d02ec6b3136c73c09e7859f0d0e4e2c4c07b49b:
Linux 5.12-rc4 (2021-03-21 14:56:43 -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.12/dm-fixes-2
for you to fetch changes up to 4edbe1d7bcffcd6269f3b5eb63f710393ff2ec7a:
dm ioctl: fix out of bounds array access when no devices (2021-03-26 14:51:50 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix DM verity target's optional argument processing.
- Fix DM core's zoned model and zone sectors checks.
- Fix spurious "detected capacity change" pr_info() when creating new
DM device.
- Fix DM ioctl out of bounds array access in handling of
DM_LIST_DEVICES_CMD when no devices exist.
----------------------------------------------------------------
JeongHyeon Lee (1):
dm verity: fix DM_VERITY_OPTS_MAX value
Mikulas Patocka (2):
dm: don't report "detected capacity change" on device creation
dm ioctl: fix out of bounds array access when no devices
Shin'ichiro Kawasaki (1):
dm table: Fix zoned model check and zone sectors check
drivers/md/dm-ioctl.c | 2 +-
drivers/md/dm-table.c | 33 +++++++++++++++++++++++++--------
drivers/md/dm-verity-target.c | 2 +-
drivers/md/dm-zoned-target.c | 2 +-
drivers/md/dm.c | 5 ++++-
include/linux/device-mapper.h | 15 ++++++++++++++-
6 files changed, 46 insertions(+), 13 deletions(-)
next reply other threads:[~2021-03-26 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 19:19 Mike Snitzer [this message]
2021-03-26 19:19 ` [git pull] device mapper fixes for 5.12-rc5 Mike Snitzer
2021-03-26 19:26 ` [dm-devel] " pr-tracker-bot
2021-03-26 19:26 ` 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=20210326191949.GA24195@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jhs2.lee@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=shinichiro.kawasaki@wdc.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.