Your message dated Tue, 23 Dec 2014 15:34:50 +0100 with message-id <[🔎] 20141223143450.GB4592@andromeda.fritz.box> has caused the report #769576, regarding linux: Btrfs goes forced readonly when qgroup already exists to be marked as having been forwarded to the upstream software author(s) Ubuntu Kernel Team <kernel-team@lists.ubuntu.com> (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.) -- 769576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769576 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>
- Cc: 769576-forwarded@bugs.debian.org, 769576@bugs.debian.org
- Subject: Re: linux: Btrfs goes forced readonly when qgroup already exists
- From: "Sebastiaan L. Zoutendijk" <baszoutendijk@gmail.com>
- Date: Tue, 23 Dec 2014 15:34:50 +0100
- Message-id: <[🔎] 20141223143450.GB4592@andromeda.fritz.box>
- In-reply-to: <[🔎] 20141223135224.GA4592@andromeda.fritz.box>
- References: <20141114165117.GA7388@andromeda.fritz.box> <20141126141259.GA3648@andromeda.fritz.box> <20141127184120.GA3345@andromeda.fritz.box> <[🔎] 20141223135224.GA4592@andromeda.fritz.box>
Dear Ubuntu Kernel Team, I would like to request an upstream patch [1] to be applied to the 3.16 kernel. This patch prevents Btrfs filesystems from going readonly when a subvolume ID is reused but the corresponding qgroup wasn't destroyed when the original subvolume was deleted. This patch has been applied by upstream to 3.17 [2], but not to 3.16 before it went EOL. For more details on the bug, please have a look at the Debian bug log [3]. That log also contains instructions to reproduce the bug, dmesg output, and my tests of the patch on various kernel versions. [1] https://patchwork.kernel.org/patch/4739211/ [2] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=fe9133f10ca56e54c5f5075a802bc08e61ad8456 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769576 [Please keep 769576-forwarded@bugs.debian.org in the CC, this will log your reply in the Debian bug tracker. If you also want your reply to be sent on to the Debian Kernel Team, please keep 769576@bugs.debian.org in the CC.]
--- End Message ---