linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: linux-f2fs-devel@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Namjae Jeon <namjae.jeon@samsung.com>,
	Amit Sahrawat <a.sahrawat@samsung.com>
Subject: Re: [PATCH 1/2] f2fs: reorganize f2fs_vm_page_mkwrite
Date: Mon, 29 Apr 2013 11:41:20 +0900	[thread overview]
Message-ID: <1367203280.16581.3.camel@kjgkr> (raw)
In-Reply-To: <1367107458-2439-1-git-send-email-linkinjeon@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2037 bytes --]

Hi,

2013-04-28 (일), 09:04 +0900, Namjae Jeon:
> From: Namjae Jeon <namjae.jeon@samsung.com>
> 
> Few things can be changed in the default mkwrite function
> 1) Make file_update_time at the start before acquiring any lock
> 2) the condition page_offset(page) >= i_size_read(inode) should be
>  changed to page_offset(page) > i_size_read
> 3) Move wait_on_page_writeback.
> 
> Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
> Signed-off-by: Amit Sahrawat <a.sahrawat@samsung.com>
> ---
>  fs/f2fs/file.c |   12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index 5cc4dd8..dc76f9b 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -63,9 +63,10 @@ static int f2fs_vm_page_mkwrite(struct vm_area_struct *vma,
>  	f2fs_put_dnode(&dn);
>  	mutex_unlock_op(sbi, ilock);
>  
> +	file_update_time(vma->vm_file);

Should we update time even if error is occurred below?

>  	lock_page(page);
>  	if (page->mapping != inode->i_mapping ||
> -			page_offset(page) >= i_size_read(inode) ||
> +			page_offset(page) > i_size_read(inode) ||

Why? IMO, there was no problem.

>  			!PageUptodate(page)) {
>  		unlock_page(page);
>  		err = -EFAULT;
> @@ -76,10 +77,7 @@ static int f2fs_vm_page_mkwrite(struct vm_area_struct *vma,
>  	 * check to see if the page is mapped already (no holes)
>  	 */
>  	if (PageMappedToDisk(page))
> -		goto out;
> -
> -	/* fill the page */
> -	wait_on_page_writeback(page);
> +		goto mapped;
>  
>  	/* page is wholly or partially inside EOF */
>  	if (((page->index + 1) << PAGE_CACHE_SHIFT) > i_size_read(inode)) {
> @@ -90,7 +88,9 @@ static int f2fs_vm_page_mkwrite(struct vm_area_struct *vma,
>  	set_page_dirty(page);
>  	SetPageUptodate(page);
>  
> -	file_update_time(vma->vm_file);
> +mapped:
> +	/* fill the page */
> +	wait_on_page_writeback(page);
>  out:
>  	sb_end_pagefault(inode->i_sb);
>  	return block_page_mkwrite_return(err);

-- 
Jaegeuk Kim
Samsung

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-04-29  2:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-28  0:04 [PATCH 1/2] f2fs: reorganize f2fs_vm_page_mkwrite Namjae Jeon
2013-04-29  2:41 ` Jaegeuk Kim [this message]
2013-04-29 11:05   ` Namjae Jeon

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=1367203280.16581.3.camel@kjgkr \
    --to=jaegeuk.kim@samsung.com \
    --cc=a.sahrawat@samsung.com \
    --cc=linkinjeon@gmail.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namjae.jeon@samsung.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;
as well as URLs for NNTP newsgroup(s).