Hi Linus,
The following changes since commit 9e0babf2c06c73cda2c0cd37a1653d823adb40ec:
Linux 5.2-rc5 (2019-06-16 08:49:45 -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.2/dm-fixes-2
for you to fetch changes up to 2eba4e640b2c4161e31ae20090a53ee02a518657:
dm verity: use message limit for data block corruption message (2019-06-25 14:09:14 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix incorrect uses of kstrndup and DM logging macros in DM's early
init code.
- Fix DM log-writes target's handling of super block sectors so updates
are made in order through use of completion.
- Fix DM core's argument splitting code to avoid undefined behaviour
reported as a side-effect of UBSAN analysis on ppc64le.
- Fix DM verity target to limit the amount of error messages that can
result from a corrupt block being found.
----------------------------------------------------------------
Gen Zhang (1):
dm init: fix incorrect uses of kstrndup()
Jerome Marchand (1):
dm table: don't copy from a NULL pointer in realloc_argv()
Milan Broz (1):
dm verity: use message limit for data block corruption message
Stephen Boyd (1):
dm init: remove trailing newline from calls to DMERR() and DMINFO()
zhangyi (F) (1):
dm log writes: make sure super sector log updates are written in order
drivers/md/dm-init.c | 10 +++++-----
drivers/md/dm-log-writes.c | 23 +++++++++++++++++++++--
drivers/md/dm-table.c | 2 +-
drivers/md/dm-verity-target.c | 4 ++--
4 files changed, 29 insertions(+), 10 deletions(-)
