[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170310002106.GD30285@linux.intel.com>
Date: Thu, 9 Mar 2017 17:21:06 -0700
From: Ross Zwisler <ross.zwisler@...ux.intel.com>
To: Jeff Layton <jlayton@...hat.com>
Cc: viro@...iv.linux.org.uk, akpm@...ux-foundation.org,
konishi.ryusuke@....ntt.co.jp, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-nilfs@...r.kernel.org, ross.zwisler@...ux.intel.com,
jack@...e.cz, neilb@...e.com, openosd@...il.com, adilger@...ger.ca,
James.Bottomley@...senPartnership.com
Subject: Re: [PATCH v2 5/9] dax: set error in mapping when writeback fails
On Wed, Mar 08, 2017 at 11:29:30AM -0500, Jeff Layton wrote:
> In order to get proper error codes from fsync, we must set an error in
> the mapping range when writeback fails.
>
> Signed-off-by: Jeff Layton <jlayton@...hat.com>
Yep, paired with the changes to filmap_write_and_wait() and
filemap_write_and_wait_range(), this seems fine.
Reviewed-by: Ross Zwisler <ross.zwisler@...ux.intel.com>
Powered by blists - more mailing lists