All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lachlan McIlroy <lmcilroy@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: limit group search loop for non-extent files
Date: Sun, 5 May 2013 20:26:35 -0400 (EDT)	[thread overview]
Message-ID: <2128465386.19191575.1367799995911.JavaMail.root@redhat.com> (raw)
In-Reply-To: <5184230E.6020500@redhat.com>

----- Original Message -----
> From: Lachlan McIlroy <lmcilroy@redhat.com>
> 
> In the case where we are allocating for a non-extent file,
> we must limit the groups we allocate from to those below
> 2^32 blocks, and ext4_mb_regular_allocator() attempts to
> do this initially by putting a cap on ngroups for the
> subsequent search loop.
> 
> However, the initial target group comes in from the
> allocation context (ac), and it may already be beyond
> the artificially limited ngroups.  In this case,
> the limit
> 
> 	if (group == ngroups)
> 		group = 0;
> 
> at the top of the loop is never true, and the loop will
> run away.
> 
> Catch this case inside the loop and reset the search to
> start at group 0.
> 
> [sandeen@redhat.com: add commit msg & comments]
> 
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
> 
> p.s. I suppose this limit could go after the assignment
> from ac->ac_g_ex.fe_group, depending on your sense
> of style...
> 
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index ee6614b..f54baee 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -1994,7 +1994,11 @@ repeat:
>  		group = ac->ac_g_ex.fe_group;
>  
>  		for (i = 0; i < ngroups; group++, i++) {
> -			if (group == ngroups)
> +			/*
> +			 * Artificially restricted ngroups for non-extent
> +			 * files makes group > ngroups possible on first loop.
> +			 */
> +			if (group >= ngroups)
>  				group = 0;
>  
>  			/* This now checks without needing the buddy page */
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Thanks for following through with this Eric.  Looks good to me.

  reply	other threads:[~2013-05-06  0:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 20:50 [PATCH] ext4: limit group search loop for non-extent files Eric Sandeen
2013-05-06  0:26 ` Lachlan McIlroy [this message]
2013-05-06  3:08 ` Theodore Ts'o
2013-05-06  4:56   ` Lachlan McIlroy
2013-05-06 13:48     ` Theodore 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=2128465386.19191575.1367799995911.JavaMail.root@redhat.com \
    --to=lmcilroy@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.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.