mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Quorum Laval <quorum.laval@gmail.com>, shaggy@kernel.org
Cc: jfs-discussion@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] jfs: Jump to error_out when filemap_fdatawait fails
Date: Tue, 23 Aug 2016 09:57:11 -0500	[thread overview]
Message-ID: <fd3daddc-b529-79e4-5f2a-13099a07e01d@oracle.com> (raw)
In-Reply-To: <997dc120ca508e8a2e757f201cca29f4dbee395d.1471896658.git.quorum.laval@gmail.com>

On 08/22/2016 03:28 PM, Quorum Laval wrote:
> filemap_fdatawait may fail, so check the return value and jump to
> error_out in the case of error.
> 
> Signed-off-by: Quorum Laval <quorum.laval@gmail.com>

These look good, but I don't see why these shouldn't be combined into a
single patch.

Thanks,
Dave

> ---
>  fs/jfs/resize.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/jfs/resize.c b/fs/jfs/resize.c
> index 90b3bc2..b0322da 100644
> --- a/fs/jfs/resize.c
> +++ b/fs/jfs/resize.c
> @@ -379,7 +379,10 @@ int jfs_extendfs(struct super_block *sb, s64 newLVSize, int newLogSize)
>  	 * cached in meta-data cache, and not written out
>  	 * by txCommit();
>  	 */
> -	filemap_fdatawait(ipbmap->i_mapping);
> +	rc = filemap_fdatawait(ipbmap->i_mapping);
> +	if (rc)
> +		goto error_out;
> +
>  	filemap_write_and_wait(ipbmap->i_mapping);
>  	diWriteSpecial(ipbmap, 0);
>  
> 

      parent reply	other threads:[~2016-08-23 17:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22 20:28 Quorum Laval
2016-08-22 20:29 ` [PATCH 2/2] jfs: jump to error_out when filemap_write_and_wait fails Quorum Laval
2016-08-23 14:57 ` Dave Kleikamp [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=fd3daddc-b529-79e4-5f2a-13099a07e01d@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quorum.laval@gmail.com \
    --cc=shaggy@kernel.org \
    /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

all inboxes | Powered by JetHome®