From:   yangerkun <yangerkun@huawei.com>
To:     <jack@suse.cz>
CC:     <miaoxie@huawei.com>, <yi.zhang@huawei.com>, <houtao1@huawei.com>,
        <yangerkun@huawei.com>, <linux-ext4@vger.kernel.org>
Subject: [PATCH 0/2] fix a bug in ext2_max_size
Date:   Wed, 23 Jan 2019 21:14:07 +0800
Message-ID: <20190123131409.126156-1-yangerkun@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-ext4-owner@vger.kernel.org
Precedence: bulk

When mkfs.ext2 with '-b 65536' and mount(arm 64KB page size),
function mount_fs will trigger WARNNING since ext2_max_size will
return value less than 0. Also, we cannot write any file in this
fs since the sb->maxbytes is less than 0.

Fix it by get the exact max file size.

yangerkun (2):
  ext2: remove static of ext2_block_to_path
  ext2: get the exact max filesize in ext2_max_size

 fs/ext2/ext2.h  |   1 +
 fs/ext2/inode.c |  16 ++++----
 fs/ext2/super.c | 115 ++++++++++++++++++++++++++++++++++++++++++++------------
 3 files changed, 101 insertions(+), 31 deletions(-)

-- 
2.9.5