summaryrefslogtreecommitdiff
path: root/drivers/vhost
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2019-06-28 03:48:21 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2019-06-28 03:48:21 +0300
commit65ee21eb633c644501185502d51831c4dee22c7b (patch)
treed94d06edeacac6efd8767b6440f717ead66c16bf /drivers/vhost
parent7a702b4e82d8730d6964bfd98b3b024c126e9846 (diff)
parent2eba4e640b2c4161e31ae20090a53ee02a518657 (diff)
downloadlinux-65ee21eb633c644501185502d51831c4dee22c7b.tar.xz
Merge tag 'for-5.2/dm-fixes-2' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm
Pull device mapper fixes from Mike Snitzer: - 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. * tag 'for-5.2/dm-fixes-2' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm: dm verity: use message limit for data block corruption message dm table: don't copy from a NULL pointer in realloc_argv() dm log writes: make sure super sector log updates are written in order dm init: remove trailing newline from calls to DMERR() and DMINFO() dm init: fix incorrect uses of kstrndup()
Diffstat (limited to 'drivers/vhost')
0 files changed, 0 insertions, 0 deletions