From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: LVM snapshot broke between 4.14 and 4.16 To: Linus Torvalds , wgh@torlan.ru Cc: Ilya Dryomov , Jens Axboe , linux-block , Linux Kernel Mailing List , Sagi Grimberg , Mike Snitzer , dm-devel@redhat.com References: <226835ba-2197-b850-6e5b-8ba14f7fd016@torlan.ru> <93bff248-6897-4867-841b-2dace11597de@torlan.ru> <1ec0a220-d5b0-1c27-e63b-c4d3f4ce9d77@torlan.ru> From: Zdenek Kabelac Message-ID: Date: Fri, 3 Aug 2018 15:31:18 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed List-ID: Dne 2.8.2018 v 23:52 Linus Torvalds napsal(a): > On Thu, Aug 2, 2018 at 2:39 PM WGH wrote: >> >> I've just found one public report of this bug, though: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900442 > > Yeah, it does sound like we should fix this issue. > Hi IMHO (as the author of fixing lvm2 patch) user should not be upgrading kernels and keep running older lvm2 user-land tool (and there are very good reasons for this). Kernel had a bug which has been fixed, lvm2 misused this kernel bug and was also fixed. Keeping kernel bug present allowing certain device to write to read-only devices can be possibly seen as some security risk. Also the number of users who ever create a read-only snapshot is probably very low. Maybe there could be some 'dm-snapshot' loading modinfo option to allowing to create in case user really wants to have this bug being present in kernel (reinstantiate old buggy logic), but on default the user should get error when it tries to write to read-only volume and should upgrade lvm2. Regards Zdenek