From: Ritesh Harjani <riteshh@linux.ibm.com>
To: Ye Bin <yebin10@huawei.com>,
adilger.kernel@dilger.ca, jack@suse.com,
linux-ext4@vger.kernel.org
Cc: jack@suse.cz, tytso@mit.edu
Subject: Re: [PATCH v5 1/2] ext4: Discard preallocations before releasing group lock
Date: Fri, 18 Sep 2020 14:37:15 +0530 [thread overview]
Message-ID: <0f17c3a5-2785-939b-47c5-55d39b4bf67b@linux.ibm.com> (raw)
In-Reply-To: <20200916113859.1556397-2-yebin10@huawei.com>
On 9/16/20 5:08 PM, Ye Bin wrote:
> From: Jan Kara <jack@suse.cz>
>
> ext4_mb_discard_group_preallocations() can be releasing group lock with
> preallocations accumulated on its local list. Thus although
> discard_pa_seq was incremented and concurrent allocating processes will
> be retrying allocations, it can happen that premature ENOSPC error is
> returned because blocks used for preallocations are not available for
> reuse yet. Make sure we always free locally accumulated preallocations
> before releasing group lock.
>
> Fixes: 07b5b8e1ac40 ("ext4: mballoc: introduce pcpu seqcnt for freeing PA to improve ENOSPC handling")
> Signed-off-by: Jan Kara <jack@suse.cz>
> Signed-off-by: Ye Bin <yebin10@huawei.com>
> Reviewed-by: Ritesh Harjani <riteshh@linux.ibm.com>
> ---
> fs/ext4/mballoc.c | 28 +++++++++++-----------------
> 1 file changed, 11 insertions(+), 17 deletions(-)
>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index 132c118d12e1..f736819a381b 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -4215,22 +4215,6 @@ ext4_mb_discard_group_preallocations(struct super_block *sb,
> 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) {
> - busy = 0;
> - ext4_unlock_group(sb, group);
> - cond_resched();
> - goto repeat;
> - }
> -
> - /* found anything to free? */
> - if (list_empty(&list)) {
> - BUG_ON(free != 0);
> - mb_debug(sb, "Someone else may have freed PA for this group %u\n",
> - group);
> - goto out;
> - }
> -
> /* now free all selected PAs */
> list_for_each_entry_safe(pa, tmp, &list, u.pa_tmp_list) {
>
> @@ -4248,7 +4232,17 @@ ext4_mb_discard_group_preallocations(struct super_block *sb,
> call_rcu(&(pa)->u.pa_rcu, ext4_mb_pa_callback);
> }
>
> -out:
> + /* if we still need more blocks and some PAs were used, try again */
> + if (free < needed && busy) {
> + ext4_unlock_group(sb, group);
> + cond_resched();
> + busy = 0;
> + /* Make sure we increment discard_pa_seq again */
> + needed -= free;
> + free = 0;
Oops sorry about getting back to this.
But if we are making free 0 here so we may return a wrong free value
when we return from this function. We should fix that by also accounting
previous freed blocks at the time of final return from this function.
-ritesh
> + goto repeat;
> + }
> +
> ext4_unlock_group(sb, group);
> ext4_mb_unload_buddy(&e4b);
> put_bh(bitmap_bh);
>
next prev parent reply other threads:[~2020-09-18 9:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 11:38 [PATCH v5 0/2] Fix dead loop in ext4_mb_new_blocks Ye Bin
2020-09-16 11:38 ` [PATCH v5 1/2] ext4: Discard preallocations before releasing group lock Ye Bin
2020-09-18 9:07 ` Ritesh Harjani [this message]
2020-09-18 9:56 ` Jan Kara
2020-09-24 15:00 ` Theodore Y. Ts'o
2020-09-24 15:12 ` Jan Kara
2020-09-24 14:58 ` Theodore Y. Ts'o
2020-09-16 11:38 ` [PATCH v5 2/2] ext4: Fix dead loop in ext4_mb_new_blocks Ye Bin
2020-09-24 14:59 ` Theodore Y. Ts'o
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=0f17c3a5-2785-939b-47c5-55d39b4bf67b@linux.ibm.com \
--to=riteshh@linux.ibm.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yebin10@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox