Your message dated Thu, 1 Sep 2022 16:40:57 +0200 with message-id <YxDEeZApuNlaSY12@eldamar.lan> and subject line Re: Bug#1017915: btrfs: space cache corruption and potential double allocations has caused the Debian Bug report #1017915, regarding btrfs: space cache corruption and potential double allocations to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1017915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017915 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: btrfs: space cache corruption and potential double allocations
- From: Christoph Anton Mitterer <calestyo@scientia.org>
- Date: Mon, 22 Aug 2022 15:00:17 +0200
- Message-id: <166117321776.13893.12709070482257150552.reportbug@heisenberg.scientia.org>
Source: linux Version: 5.18.16-1 Severity: important Tags: upstream patch Hey. This is merely a heads up, that a potentially pretty nasty data corruption issue has been found in btrfs. As far as I understand: It was introduced in 5.12, has the highest chances to occur with free space cache v2, but may also happen with v1 or even nospace_cache. v2 was made default with btrfs-progs 5.15. It seems that it may in principle affect data and metadata, so could range from single file corruptions to complete fs breakage? The patch, which AFAICS hasn't been submitted to linux-stable yet, can be found here: https://lore.kernel.org/linux-btrfs/cover.1660690698.git.osandov@fb.com/ A more in-depth description can be found in it's first commit. Some others and I myself have asked some further questions about the issue (how one can detect any corruptions, and so on), which can also be found in the very same mail thread. Not sure if the above patch is already production read, but at least it would be quite helpful if it could be cherry-picked for testing/sid as soon as it has landed in linux-stable. Thanks, Chris.
--- End Message ---
--- Begin Message ---
- To: Christoph Anton Mitterer <calestyo@scientia.org>, 1017915-done@bugs.debian.org
- Subject: Re: Bug#1017915: btrfs: space cache corruption and potential double allocations
- From: Salvatore Bonaccorso <carnil@debian.org>
- Date: Thu, 1 Sep 2022 16:40:57 +0200
- Message-id: <YxDEeZApuNlaSY12@eldamar.lan>
- In-reply-to: <[🔎] fb3d6e2550088c65e421f4c6ac334c3d7dc58d5a.camel@scientia.org>
- References: <166117321776.13893.12709070482257150552.reportbug@heisenberg.scientia.org> <handler.1017915.B.166117323526082.ack@bugs.debian.org> <166117321776.13893.12709070482257150552.reportbug@heisenberg.scientia.org> <[🔎] fb3d6e2550088c65e421f4c6ac334c3d7dc58d5a.camel@scientia.org>
Source: linux Source-Version: 5.19.6-1 On Thu, Sep 01, 2022 at 03:43:44PM +0200, Christoph Anton Mitterer wrote: > Control: tags -1 + patch > > Hey. > > The patch for this has been merged in the stable kernels... could you > please cherry pick respectively update the sid kernel ASAP? > > https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.19.6 > > commit: a2e54eb64229f07f917b05d0c323604fda9b89f7 > btrfs: fix space cache corruption and potential double allocations 5.19.6-1 has been uploaded earlier today. Regards, Salvatore
--- End Message ---