From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:38890 "EHLO mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725776AbeLBL7I (ORCPT ); Sun, 2 Dec 2018 06:59:08 -0500 Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 4BF312AA66 for ; Sun, 2 Dec 2018 11:59:05 +0000 (UTC) From: bugzilla-daemon@bugzilla.kernel.org To: linux-ext4@vger.kernel.org Subject: [Bug 201685] ext4 file system corruption Date: Sun, 02 Dec 2018 11:59:04 +0000 Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-ext4-owner@vger.kernel.org List-ID: https://bugzilla.kernel.org/show_bug.cgi?id=201685 --- Comment #137 from Marc Burkhardt (marc@osknowledge.org) --- (In reply to jaapbuurman from comment #135) > Doesn't the Linux kernel team have any procedures in place for when such a > critical bug is found? There are many people running this "stable" 4.19 > branch, many of whom are unaware of this bug. Shouldn't the stable branch be > rolled back to the last known good version? Going back to 4.18 is certainly > a better option, but people unaware of this bug might still be running 4.19. That would mean depublishing of the 4.19 release as a whole as nobody knows _what_ exactly to roll back. And if one would know, they would fix the bug instead. I cannot remember such a scenario/bug in the past... -- You are receiving this mail because: You are watching the assignee of the bug.