Hi Christoph,
On Thu, Mar 14, 2019 at 08:06:52PM +0100, Christoph Anton Mitterer wrote:
> Hey Ben, Salvatore.
>
> Thanks for cherry-picking the bug for unstable.
>
> AFAIU stretch and jessie[-backports] should be affected as well.
> Shouldn't it go there, too?
Yes it needs to be adressed there
Hey Ben, Salvatore.
Thanks for cherry-picking the bug for unstable.
AFAIU stretch and jessie[-backports] should be affected as well.
Shouldn't it go there, too?
At least at the upstream mailing list it was said[0] the the bug was
introduced around October 2008, which should be roughly kernel
Control: tags -1 + pending
On Sun, Feb 24, 2019 at 09:40:59AM +0100, Salvatore Bonaccorso wrote:
> Control: found -1 4.3~rc5-1~exp1
> Control: tags -1 + upstream patch
>
> Upstream patch submission at
> https://lore.kernel.org/linux-btrfs/20190214151720.23563-1-fdman...@kernel.org/
Pending in
Control: found -1 4.3~rc5-1~exp1
Control: tags -1 + upstream patch
Upstream patch submission at
https://lore.kernel.org/linux-btrfs/20190214151720.23563-1-fdman...@kernel.org/
Regards,
Salvatore
Here's the "proper" patch:
https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg85515.html
Source: linux
Version: 4.19.20-1
Severity: critical
Tags: upstream patch
Justification: causes serious data loss
Hi.
Apparently there was a longer existing data corruption bug in btrfs[0],
AFAIU it happened when compression was used together with holes in data
and there was *no* recognition by
6 matches
Mail list logo
