From: Jan Kara <jack@suse.cz>
To: Zhang Zhen <zhenzhang.zhang@huawei.com>
Cc: "tytso@mit.edu" <tytso@mit.edu>, Jan Kara <jack@suse.cz>,
adilger.kernel@dilger.ca,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] fs/ext4: fix potential endless loop in ext4_mb_discard_group_preallocations()
Date: Wed, 16 Sep 2015 21:45:10 +0200 [thread overview]
Message-ID: <20150916194510.GC29530@quack.suse.cz> (raw)
In-Reply-To: <55E42270.9040503@huawei.com>
On Mon 31-08-15 17:46:24, Zhang Zhen wrote:
> In ext4_mb_discard_group_preallocations(), if free is always less than needed,
> and some PAs are always used in every loop, it will be endless loop.
>
> Here we pick a random value to limit the max number of loop.
Were you able to trigger this in practice or is it just a theoretical
concern?
My slight concern is that in theory we could prematurely declare ENOSPC
with this patch since ext4_mb_discard_preallocations() doesn't reliably
discard all the preallocations anymore. But probably that's acceptable.
But we should add a comment before ext4_mb_discard_group_preallocations()
saying that the functions needn't free all the preallocations.
Honza
>
> Signed-off-by: Zhang Zhen <zhenzhang.zhang@huawei.com>
> ---
> fs/ext4/mballoc.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index 34b610e..553fbde 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -3836,6 +3836,7 @@ ext4_mb_discard_group_preallocations(struct super_block *sb,
> int err;
> int busy = 0;
> int free = 0;
> + int tried = 0;
>
> mb_debug(1, "discard preallocation for group %u\n", group);
>
> @@ -3886,9 +3887,11 @@ repeat:
> list_add(&pa->u.pa_tmp_list, &list);
> }
>
> - /* if we still need more blocks and some PAs were used, try again */
> - if (free < needed && busy) {
> + /* if we still need more blocks and some PAs were used, try again,
> + here 20 is a ramdon value. */
> + if (free < needed && busy && tried < 20) {
> busy = 0;
> + tried++;
> ext4_unlock_group(sb, group);
> cond_resched();
> goto repeat;
> --
> 1.9.1
>
>
> .
>
>
>
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2015-09-16 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1441013790-87948-1-git-send-email-zhenzhang.zhang@huawei.com>
2015-08-31 9:46 ` [PATCH] fs/ext4: fix potential endless loop in ext4_mb_discard_group_preallocations() Zhang Zhen
2015-08-31 22:34 ` Andreas Dilger
2015-09-01 1:16 ` Zhang Zhen
2015-09-01 6:41 ` [PATCH v2] " Zhang Zhen
2015-09-16 19:45 ` Jan Kara [this message]
2015-09-17 1:27 ` [PATCH] " Zhang Zhen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150916194510.GC29530@quack.suse.cz \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=zhenzhang.zhang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.