linux-kernel - Re: Regression in 4.14.147, 4.19.76, 5.2.18 leading to kernel panic on btrfs root fs mount

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20191014042023.GA31224@sasha-vm>
Date:   Mon, 14 Oct 2019 00:20:23 -0400
From:   Sasha Levin <sashal@...nel.org>
To:     Andrew Macks <andypoo@...il.com>
Cc:     stable@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Regression in 4.14.147, 4.19.76, 5.2.18 leading to kernel panic
 on btrfs root fs mount

On Sun, Oct 13, 2019 at 07:04:12PM +0300, Andrew Macks wrote:
>Was not sure the correct way to escalate this quickly enough.  I
>unfortunately discovered this issue while upgrading a server (remotely) to
>4.19.78 (longterm).
>
>*Bug 205181* <https://bugzilla.kernel.org/show_bug.cgi?id=205181> - kernel
>panic when accessing btrfs root device with f2fs in kernel
>https://bugzilla.kernel.org/show_bug.cgi?id=205181

Okay, I've backported 38fb6d0ea3429 ("f2fs: use EINVAL for superblock
with invalid magic") to 4.19 and 4.14. It'll be great if someone could
ack that backport.

Sorry for the breakage.

-- 
Thanks,
Sasha