From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 195561] Suspicious persistent EXT4-fs error:
ext4_validate_block_bitmap:395: [Proc] bg 17: block 557056: invalid block
bitmap
Date: Sun, 14 May 2017 11:41:43 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
To: linux-ext4@kernel.org
Return-path:
Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:32904 "EHLO
mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK)
by vger.kernel.org with ESMTP id S1751603AbdENLlo (ORCPT
);
Sun, 14 May 2017 07:41:44 -0400
Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1])
by mail.wl.linuxfoundation.org (Postfix) with ESMTP id D9D0928943
for ; Sun, 14 May 2017 11:41:43 +0000 (UTC)
In-Reply-To:
Sender: linux-ext4-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=195561
--- Comment #32 from Mauro Rossi (issor.oruam@gmail.com) ---
(In reply to Theodore Tso from comment #31)
> So I'm just curious. Android's fix for the problem landed in October
> 2016[1]. It's now May 2017. Why is it that so many folks are still using
> an old version of AOSP that apparently does not have this fix?
>
> [1]
> https://android.googlesource.com/platform/system/extras/+/
> c71eaf37486bed9163ad528f51de29dd56b34fd2
The reason is that commit is not in the Android release cycle,
it landed in master, but we're building nougat-x86 with latest
android-7.1.2_r11 tagged version.
The mentioned problem should affect 32 bit only, or is 64bit expected to be
affected too, with the explanations given in the commit message?
Mauro
--
You are receiving this mail because:
You are watching the assignee of the bug.