From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f181.google.com ([209.85.212.181]:36003 "EHLO mail-wi0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752965AbbIYLXx (ORCPT ); Fri, 25 Sep 2015 07:23:53 -0400 Received: by wicgb1 with SMTP id gb1so16030121wic.1 for ; Fri, 25 Sep 2015 04:23:52 -0700 (PDT) Subject: Re: commit 841df7df1962 "jbd2: avoid infinite loop when destroying aborted journal" should probably go to stable To: Roland Dreier , stable@vger.kernel.org References: Cc: Jan Kara , Theodore Ts'o From: Jiri Slaby Message-ID: <56052EC7.6070303@suse.cz> Date: Fri, 25 Sep 2015 13:23:51 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: stable-owner@vger.kernel.org List-ID: On 09/24/2015, 10:09 AM, Roland Dreier wrote: > Commit 6f6a6fda2945 "jbd2: fix ocfs2 corrupt when updating journal > superblock fails" was tagged for -stable and was picked up by at least > 3.10.y etc. However the newer commit 841df7df1962 "jbd2: avoid > infinite loop when destroying aborted journal" fixes a possible hang > caused by that earlier commit, so all stable trees that picked up > 6f6a6fda2945 should probably also pick up the fix to it. It does not apply to 3.12 at all :(. Could someone provide a backport? thanks, -- js suse labs