[dm-devel] [PATCH] dm raid: Documentaion

From: Heinz Mauelshagen Upstream commits d36a19541fe8f392778ac137d60f9be8dfdd8f9d and 2664f3c94abc7181171b7c05b2aaa76ea7d9d613 fixed a data corruptor related to reshape requests. Add missing version 1.10.1 to the documention. Signed-off-by: Heinz Mauelshagen

[dm-devel] [PATCH 1/2] dm raid: fix table line argument order in status

From: Heinz Mauelshagen Upstream commit 3a1c1ef2fd62087c3d6521de217ddb9360776658 added new table line arguments and introduced an ordering flaw. The sequence of the raid10_copies and raid10_format raid parameters got reversed which causes lvm2 userspace to fail falsely

[dm-devel] [PATCH] multipath-tools: arrange compilation options for binaries

Cc: Christophe Varoqui Cc: device-mapper development Signed-off-by: Xose Vazquez Perez --- kpartx/Makefile | 2 +- mpathpersist/Makefile | 2 +- multipath/Makefile| 2 +- multipathd/Makefile | 2 +- 4

Re: [dm-devel] dm crypt: remove an impossible condition

On Fri, Mar 17 2017 at 4:46pm -0400, Dan Carpenter wrote: > Static checkers complain that it doesn't make sense to check if "sval" > is NULL. The intention was to check if strchr() returned NULL, but in > that situation "sval" would be "NULL + 1" so the check doesn't

[dm-devel] [PATCH] dm crypt: remove an impossible condition

Static checkers complain that it doesn't make sense to check if "sval" is NULL. The intention was to check if strchr() returned NULL, but in that situation "sval" would be "NULL + 1" so the check doesn't work. We know from the sscanf() that there is a ':' character in the string so the check is

Re: [dm-devel] [BUG] Oops caused by FEC in 4.10.0

On 03/17/2017 04:35 PM, Sami Tolvanen wrote: > On Fri, Mar 17, 2017 at 12:45:00PM +0100, Milan Broz wrote: >> it still does take at least two minutes and tons of logs until even >> udev scan finishes on a device with incorrect FEC attributes. > > If dm-verity is set up with invalid arguments so

Re: [dm-devel] [BUG] Oops caused by FEC in 4.10.0

On Fri, Mar 17, 2017 at 01:27:25PM +0100, michal virgovic wrote: > I tried it too, but with correctly computed root-hash, salt, > hash-device, fec-device (using veritysetup) and the outcome is same. Do you mean the panic when destroying the dm device or the issue you saw initially? If the hashes

Re: [dm-devel] [BUG] Oops caused by FEC in 4.10.0

On Fri, Mar 17, 2017 at 12:45:00PM +0100, Milan Broz wrote: > it still does take at least two minutes and tons of logs until even > udev scan finishes on a device with incorrect FEC attributes. If dm-verity is set up with invalid arguments so that the entire partition is corrupt, it does take a

[dm-devel] [PATCH] multipath-tools: build objects for libdmmp and libmpathpersist independently

libdmmp: cc -c -O2 -g -pipe -Wall -Wextra -Wformat=2 -Werror=implicit-int -Werror=implicit-function-declaration -Werror=format-security -Wno-sign-compare -Wno-unused-parameter -Wno-clobbered -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector-strong --param=ssp-buffer-size=4 -fPIC -DLIB_STRING=\"lib64\"

[dm-devel] [PATCH] multipath-tools: add missing "-l" flag for pthread in libdmmp/Makefile

Cc: Gris Ge Cc: Christophe Varoqui Cc: device-mapper development Signed-off-by: Xose Vazquez Perez --- libdmmp/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[dm-devel] [PATCH v2] dm-zoned: Zoned block device target

The dm-zoned device mapper target provides transparent write access to zoned block devices (ZBC and ZAC compliant block devices). dm-zoned hides to the device user (a file system or an application doing raw block device accesses) any constraint imposed on write requests by the device. Write

Re: [dm-devel] [BUG] Oops caused by FEC in 4.10.0

On 03/15/2017 11:12 PM, Sami Tolvanen wrote: > On Wed, Mar 15, 2017 at 09:22:02PM +0100, michal virgovic wrote: >> This oops keeps appearing. > > This can happen if dm-verity is set up with an invalid root hash, for > example. Please test the attached patch, which limits recursion and should >