Received-SPF: pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Chengguang Xu <cgxu519@mykernel.net>
To:     jack@suse.com
Cc:     linux-ext4@vger.kernel.org, Chengguang Xu <cgxu519@mykernel.net>
Message-ID: <20191020232326.84881-1-cgxu519@mykernel.net>
Subject: [PATCH] ext2: adjust block num when retry allocation
Date:   Mon, 21 Oct 2019 07:23:26 +0800
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf8
Sender: linux-ext4-owner@vger.kernel.org
Precedence: bulk

Set block num to original *count in a case
of retrying allocation in case num < *count

Signed-off-by: Chengguang Xu <cgxu519@mykernel.net>
---
Hi Jan,

This patch is only compile-tested, I'm not sure if this
kind of unexpected condition which causes reallocation
will actually happen but baesd on the code the fix seems
correct and better.

 fs/ext2/balloc.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/fs/ext2/balloc.c b/fs/ext2/balloc.c
index e0cc55164505..924c1c765306 100644
--- a/fs/ext2/balloc.c
+++ b/fs/ext2/balloc.c
@@ -1404,6 +1404,7 @@ ext2_fsblk_t ext2_new_blocks(struct inode *inode, ext=
2_fsblk_t goal,
 =09=09 * use.  So we may want to selectively mark some of the blocks
 =09=09 * as free
 =09=09 */
+=09=09num =3D *count;
 =09=09goto retry_alloc;
 =09}
=20
--=20
2.21.0