public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Mingming Cao <cmm@us.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: tytso@mit.edu, sandeen@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: [RFC PATCH] ext4: Fix fallocate to update the file size in each transaction.
Date: Fri, 07 Mar 2008 03:30:57 -0800	[thread overview]
Message-ID: <1204889457.3627.43.camel@localhost.localdomain> (raw)
In-Reply-To: <1204887200-9929-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>

On Fri, 2008-03-07 at 16:23 +0530, Aneesh Kumar K.V wrote:
> ext4_fallocate need to update file size in each transaction. Otherwise
> ife we crash the file size won't be updated. We were also not marking
> the inode dirty after updating file size before. Also when we try to
> retry allocation due to ENOSPC make sure we reset the variable ret so
> that we actually do a retry.
> 
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> ---
>  fs/ext4/extents.c |   78 +++++++++++++++++++++--------------------------------
>  1 files changed, 31 insertions(+), 47 deletions(-)
> 
> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> index dcdf92a..09dd3c5 100644
> --- a/fs/ext4/extents.c
> +++ b/fs/ext4/extents.c
> @@ -2783,6 +2783,26 @@ int ext4_ext_writepage_trans_blocks(struct inode *inode, int num)
>  	return needed;
>  }
> 
> +static void ext4_falloc_update_inode(struct inode *inode,
> +					int mode, loff_t new_size)
> +{
> +	struct timespec now;
> +
> +	now = current_fs_time(inode->i_sb);
> +	if (!timespec_equal(&inode->i_ctime, &now))
> +		inode->i_ctime = now;
> +	/*
> +	 * Update only when preallocation was requested beyond
> +	 * the file size.
> +	 */
> +	if (!(mode & FALLOC_FL_KEEP_SIZE) &&
> +				new_size > i_size_read(inode)) {
> +		i_size_write(inode, new_size);
> +		EXT4_I(inode)->i_disksize = i_size_read(inode);

Just a minor thing, we could store new_size directly to i_disksize to
avoid calling the i_size_read() instead.


> +	}
> +
> +}
> +
>  /*
>   * preallocate space for a file. This implements ext4's fallocate inode
>   * operation, which gets called from sys_fallocate system call.
> @@ -2794,8 +2814,8 @@ long ext4_fallocate(struct inode *inode, int mode, loff_t offset, loff_t len)
>  {
>  	handle_t *handle;
>  	ext4_lblk_t block;
> +	loff_t new_size;
>  	unsigned long max_blocks;
> -	ext4_fsblk_t nblocks = 0;
>  	int ret = 0;
>  	int ret2 = 0;
>  	int retries = 0;
> @@ -2814,8 +2834,7 @@ long ext4_fallocate(struct inode *inode, int mode, loff_t offset, loff_t len)
>  		return -ENODEV;
> 
>  	block = offset >> blkbits;
> -	max_blocks = (EXT4_BLOCK_ALIGN(len + offset, blkbits) >> blkbits)
> -			- block;
> +	max_blocks = EXT4_BLOCK_ALIGN(len, blkbits) >> blkbits;
> 

Not sure about this change... Other than this looks fine to me

MIngming



  reply	other threads:[~2008-03-07 11:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07 10:53 [RFC PATCH] ext4: Fix fallocate to update the file size in each transaction Aneesh Kumar K.V
2008-03-07 11:30 ` Mingming Cao [this message]
2008-03-07 11:44   ` Aneesh Kumar K.V
2008-03-07 16:03     ` Dave Kleikamp
2008-03-07 17:59       ` Mingming Cao
2008-03-08 16:12       ` Aneesh Kumar K.V
2008-03-07 15:45 ` Eric Sandeen
2008-03-07 15:57   ` Eric Sandeen
2008-03-08 16:11   ` Aneesh Kumar K.V

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=1204889457.3627.43.camel@localhost.localdomain \
    --to=cmm@us.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox