From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail.linuxfoundation.org ([140.211.169.12]:51268 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1725876AbeHOIsJ (ORCPT
        <rfc822;stable@vger.kernel.org>); Wed, 15 Aug 2018 04:48:09 -0400
Date: Wed, 15 Aug 2018 07:57:20 +0200
From: Greg KH <gregkh@linuxfoundation.org>
To: Alistair Strachan <astrachan@google.com>
Cc: stable@vger.kernel.org, kernel-team@android.com
Subject: Re: Please apply 501228470077 ("ext4: fix check to prevent
 initializing reserved inodes") to 4.4.y and 4.9.y
Message-ID: <20180815055720.GF10151@kroah.com>
References: <CANDihLELvY4gbLonzny6+x6EbxQ3ii6RA0Mu+SuZFa_SWYJXFw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CANDihLELvY4gbLonzny6+x6EbxQ3ii6RA0Mu+SuZFa_SWYJXFw@mail.gmail.com>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Tue, Aug 14, 2018 at 12:53:49PM -0700, Alistair Strachan wrote:
> The commit 8844618d8aa7 ("ext4: only look at the bg_flags field if it
> is valid") introduced an issue which are seeing when running "adb
> remount" on Android devices with the affected kernels. This change
> appears on 4.4.y and later.
> 
> > EXT4-fs error (device vdd): ext4_has_uninit_itable:2882: comm remount svc 50: Inode table for bg 0 marked as needing zeroing
> > Kernel panic - not syncing: EXT4-fs (device vdd): panic forced after error
> 
> Looks like this fix was already picked up for 4.14.y, 4.17.y but
> (AFAIK) it isn't on anybody's radar for 4.4 and 4.9. Thanks!

This is already queued up in the 4.4 and 4.9 -rc releases.

thanks,

greg k-h