Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp6411283imm; Wed, 27 Jun 2018 07:19:09 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKuOc+cOpt0c9NFX4zYe05+G+pLbPhHmkpfoldoxVJFI4cPucgqPIcYJt+OZGWKEgpNV+nZ X-Received: by 2002:a17:902:708b:: with SMTP id z11-v6mr6269687plk.231.1530109149541; Wed, 27 Jun 2018 07:19:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530109149; cv=none; d=google.com; s=arc-20160816; b=RCGjLUDb5psKhIsrFyTT4UGBawfcoVDnn/c1J2uvcJbnXrqshs/vIa9d/i8DxK4/YL 6WBIxItKE6wB2ZtcVnIeU9LctidKJyrvITJUahY4kGVqJ+VCYFkUyF4KLXU199wUXo0m ZaS3GUksEeTP0XRguOi7D702+6ysf9UR2LOEPPrBJv7X3IOKFMhS274byOWHXUfc5V25 ZA0w6inNhWPRCKYtp5LuLAW46ZTJ0RFHktneINE0N4EGziEOYWni5090RbVEOWg596Do sXIlDa/490bG9cdsUPZANM+YZgghEnntxXq0VPj/x2w6jh4HaT+wY32RqnYIafvgrTjl Gwcw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=elwyV6RvddMTNwKBo7+XXjPohjV6LeW7TYtH5KK2/84=; b=kw9x/YWnjgn/N8nWIu72s53rniIP/2DP+F5rqe+h5Z7VSG3YZC8ZVvkeCTqrv8kSlx EjOffvONSSxwUb5RKC3cRLis1WR9oAsF4C3CYEk2YF2dCCziGwE3dZ5VEKfpejpdh0mN 27IlF60e0Qi7Z7Q0B2RuEqoO4LMQ8UiGqtgxcB7Sk0uyFDvajVvDDMuWFRdJeX0NJ8kt /RQU39mSJx6mM+MymvllYuTalgeju6UJKMVjf4BxgBmGkmmy3js9FYLS/wIPxFE3zp5J 1SmcGfBAId4lwBDWkgXRVgRiASW6/b8SKpZcgLwCYIsLN6iEr9TiUkRY2DToWWJx2Jiz roAw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@thunk.org header.s=ef5046eb header.b=ThBEaqOz; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z10-v6si3516176pgu.238.2018.06.27.07.18.54; Wed, 27 Jun 2018 07:19:09 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@thunk.org header.s=ef5046eb header.b=ThBEaqOz; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965305AbeF0OJm (ORCPT + 99 others); Wed, 27 Jun 2018 10:09:42 -0400 Received: from imap.thunk.org ([74.207.234.97]:60692 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932312AbeF0OJk (ORCPT ); Wed, 27 Jun 2018 10:09:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org; s=ef5046eb; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=elwyV6RvddMTNwKBo7+XXjPohjV6LeW7TYtH5KK2/84=; b=ThBEaqOzlNU0iyz8Js7apjOTvv BY9WwK/knPryRj8BZAGIv+MfLsXKkVADae0mPgHhbY+5e4I+Pmx2rzzA3uWn3F6aTt7obUaJN8NG8 xfpEBw3tUavP53NfphyOrETL5dNWFHEW82Z4LRD1sev1otAXBx3i+kl7/NRFY+NO+H3c=; Received: from root (helo=callcc.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.89) (envelope-from ) id 1fYB8c-0008Fo-E7; Wed, 27 Jun 2018 14:09:38 +0000 Received: by callcc.thunk.org (Postfix, from userid 15806) id 8A1157A4481; Wed, 27 Jun 2018 10:09:37 -0400 (EDT) Date: Wed, 27 Jun 2018 10:09:37 -0400 From: "Theodore Y. Ts'o" To: GaoMing Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, sorp.liqingchao@huawei.com, harry.shen@huawei.com, miaoxie@huawei.com Subject: Re: [PATCH] ext4: e2fsprogs: fix inode bitmap num not integer,incompatible for ancient android devices Message-ID: <20180627140937.GA3348@thunk.org> Mail-Followup-To: "Theodore Y. Ts'o" , GaoMing , linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, sorp.liqingchao@huawei.com, harry.shen@huawei.com, miaoxie@huawei.com References: <1530014046-62466-1-git-send-email-gaoming20@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1530014046-62466-1-git-send-email-gaoming20@huawei.com> User-Agent: Mutt/1.10.0 (2018-05-17) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 26, 2018 at 07:54:06PM +0800, GaoMing wrote: > for example, 1708 inodes every group,3 block groups, bitmap bytes are 1708/8=213.5 when the inode bitmap has some errors, e2fsprogs cannot fix it > > Signed-off-by: GaoMing File systems like this should not exist. Can you please please please make sure that any use of make_ext2fs are ripped out by the roots? What I *should* do is have e2fsck reject these file systems as completely invalid in pass 0, when we check for superblock sanity. I haven't because there are some older Android systems that use make_ext2fs. But at this point, what I am **seriously** doing is to make e2fsck reject these file systems by default, unless a setting in e2fsck.conf is set to allow them as an exception. My concern about applying this patch is that it will be taken as acceptance of e2fsprogs to fully support these sorts of invalid file systems. In particular, there is no guarantee that various tune2fs options, resize2fs, etc., will work correctly even with your patch. - Ted