All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Theodore Ts'o <tytso@mit.edu>,
	aneesh.kumar@linux.vnet.ibm.com, sct@redhat.com,
	akpm@linux-foundation.org, adilger@sun.com
Cc: stable@kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [stable] Patch Upstream: ext4: Fix s_dirty_blocks_counter if block allocation failed with nodelalloc
Date: Wed, 14 Jan 2009 15:47:48 -0800	[thread overview]
Message-ID: <20090114234748.GD24230@kroah.com> (raw)
In-Reply-To: <200901090125.n091P7CU028977@hera.kernel.org>

Hi Ted and others,

I see a bunch of ext4 / jbd2 patches were tagged as requested to go into
the -stable tree.  But there seems to not be any simple way to determine
what order these patches should go in.

Can someone please list the order of them, or resend all patches that
they request to go into the 2.6.28-stable tree (and 2.6.27 if some of
the patches apply there as well.)

thanks,

greg k-h

> commit: 0087d9fb3f29f59e8d42c8b058376d80e5adde4c
> From: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> Date: Mon, 5 Jan 2009 21:49:12 -0500
> Subject: ext4: Fix s_dirty_blocks_counter if block allocation failed with nodelalloc
> 
> With nodelalloc option we need to update the dirty block counter on
> block allocation failure. This is needed because we increment the
> dirty block counter early in the block allocation phase. Without
> the patch s_dirty_blocks_counter goes wrong so that filesystem's
> free blocks decreases incorrectly.
> 
> Tested-by: Akira Fujita <a-fujita@rs.jp.nec.com>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
> Cc: stable@kernel.org
> ---
>  fs/ext4/mballoc.c |    9 ++++++++-
>  1 files changed, 8 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index fd2294d..05d9f81 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -4541,7 +4541,7 @@ ext4_fsblk_t ext4_mb_new_blocks(handle_t *handle,
>  	}
>  	if (ar->len == 0) {
>  		*errp = -EDQUOT;
> -		return 0;
> +		goto out3;
>  	}
>  	inquota = ar->len;
>  
> @@ -4614,6 +4614,13 @@ out2:
>  out1:
>  	if (ar->len < inquota)
>  		DQUOT_FREE_BLOCK(ar->inode, inquota - ar->len);
> +out3:
> +	if (!ar->len) {
> +		if (!EXT4_I(ar->inode)->i_delalloc_reserved_flag)
> +			/* release all the reserved blocks if non delalloc */
> +			percpu_counter_sub(&sbi->s_dirtyblocks_counter,
> +						reserv_blks);
> +	}
>  
>  	return block;
>  }
> -- 
> 1.6.0.2
> 
> _______________________________________________
> stable mailing list
> stable@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/stable

       reply	other threads:[~2009-01-14 23:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200901090125.n091P7CU028977@hera.kernel.org>
2009-01-14 23:47 ` Greg KH [this message]
2009-01-15  1:30   ` [stable] Patch Upstream: ext4: Fix s_dirty_blocks_counter if block allocation failed with nodelalloc Theodore Tso
2009-01-15  4:16     ` Greg KH

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=20090114234748.GD24230@kroah.com \
    --to=greg@kroah.com \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sct@redhat.com \
    --cc=stable@kernel.org \
    --cc=tytso@mit.edu \
    /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.