From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 3 Aug 2018 09:31:03 -0400 From: Mike Snitzer To: Linus Torvalds Cc: wgh@torlan.ru, Ilya Dryomov , Jens Axboe , linux-block , Linux Kernel Mailing List , Sagi Grimberg , dm-devel@redhat.com Subject: Re: LVM snapshot broke between 4.14 and 4.16 Message-ID: <20180803133102.GA3092@redhat.com> References: <226835ba-2197-b850-6e5b-8ba14f7fd016@torlan.ru> <93bff248-6897-4867-841b-2dace11597de@torlan.ru> <1ec0a220-d5b0-1c27-e63b-c4d3f4ce9d77@torlan.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: List-ID: On Thu, Aug 02 2018 at 5:52pm -0400, Linus Torvalds wrote: > 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. Debian is notorious for having a stale and/or custom lvm2. Generally speaking, it is recommended that lvm2 not be older than the kernel (but the opposite is fine). Given the narrow scope of users impacted (read-only snapshot creation is very niche, certainly not the default): I don't think it is worth making fiddly changes in dm-snapshot to warn the user and override the permissions for the cow device. Mike