linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-f2fs-devel@lists.sourceforge.net, kernel-janitors@vger.kernel.org
Subject: Re: [patch] f2fs: checking for IS_ERR() instead of NULL
Date: Thu, 09 Jan 2014 18:56:27 +0900	[thread overview]
Message-ID: <1389261387.3035.7.camel@kjgkr> (raw)
In-Reply-To: <20140109052825.GB1265@elgon.mountain>

Thank you for the patch.
This was already fixed in the original patch with an issue trigger by
Chao Yu before.
I rebased it before, so that it seems you need to pull the f2fs again.
Thanks,

2014-01-09 (목), 08:28 +0300, Dan Carpenter:
> grab_cache_page_write_begin() returns NULL on error, it doesn't return
> error pointers.
> 
> Fixes: e18c65b2ac91 ('f2fs: key functions to handle inline data')
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> 
> diff --git a/fs/f2fs/inline.c b/fs/f2fs/inline.c
> index 69a923e38f0c..e0d800a1d79f 100644
> --- a/fs/f2fs/inline.c
> +++ b/fs/f2fs/inline.c
> @@ -131,8 +131,8 @@ int f2fs_convert_inline_data(struct inode *inode, pgoff_t to_size)
>  		return 0;
>  
>  	page = grab_cache_page_write_begin(inode->i_mapping, 0, AOP_FLAG_NOFS);
> -	if (IS_ERR(page))
> -		return PTR_ERR(page);
> +	if (!page)
> +		return -ENOMEM;
>  
>  	err = __f2fs_convert_inline_data(inode, page);
>  	f2fs_put_page(page, 1);

-- 
Jaegeuk Kim
Samsung

--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2014-01-09  9:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09  5:28 [patch] f2fs: checking for IS_ERR() instead of NULL Dan Carpenter
2014-01-09  9:56 ` Jaegeuk Kim [this message]

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=1389261387.3035.7.camel@kjgkr \
    --to=jaegeuk.kim@samsung.com \
    --cc=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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).