On Fri, Aug 03, 2018 at 08:56:36PM +0100, Alasdair G Kergon wrote: > Anything passing in version 4.37.0 or earlier (which is the version in If taking this approach, it might be better to use the current version i.e. where we add the kernel-side fix. IOW anything compiling against a uapi header taken from a kernel up to now will see the old behaviour, but anything newer (after we next increment the kernel dm version) will be required to change its userspace code if it has this problem in it. The problematic versions of lvm2 ship with versions up to and including 4.36.0 in this field so should be caught either way. Alasdair
