Re: [PATCH v2 6/9] mm: set mapping error when launder_pages fails

2017-03-08 Thread NeilBrown
On Thu, Mar 09 2017, Trond Myklebust wrote: > On Wed, 2017-03-08 at 11:29 -0500, Jeff Layton wrote: >> If launder_page fails, then we hit a problem writing back some inode >> data. Ensure that we communicate that fact in a subsequent fsync >> since >> another task could still have it open for

Re: [PATCH v2 6/9] mm: set mapping error when launder_pages fails

2017-03-08 Thread NeilBrown
On Thu, Mar 09 2017, Trond Myklebust wrote: > On Wed, 2017-03-08 at 11:29 -0500, Jeff Layton wrote: >> If launder_page fails, then we hit a problem writing back some inode >> data. Ensure that we communicate that fact in a subsequent fsync >> since >> another task could still have it open for

Re: [PATCH v2 6/9] mm: set mapping error when launder_pages fails

2017-03-08 Thread Trond Myklebust
On Wed, 2017-03-08 at 13:38 -0500, Jeff Layton wrote: > On Wed, 2017-03-08 at 18:01 +, Trond Myklebust wrote: > > On Wed, 2017-03-08 at 11:29 -0500, Jeff Layton wrote: > > > If launder_page fails, then we hit a problem writing back some > > > inode > > > data. Ensure that we communicate that

Re: [PATCH v2 6/9] mm: set mapping error when launder_pages fails

2017-03-08 Thread Trond Myklebust
On Wed, 2017-03-08 at 13:38 -0500, Jeff Layton wrote: > On Wed, 2017-03-08 at 18:01 +, Trond Myklebust wrote: > > On Wed, 2017-03-08 at 11:29 -0500, Jeff Layton wrote: > > > If launder_page fails, then we hit a problem writing back some > > > inode > > > data. Ensure that we communicate that

Re: [PATCH v2 6/9] mm: set mapping error when launder_pages fails

2017-03-08 Thread Jeff Layton
On Wed, 2017-03-08 at 18:01 +, Trond Myklebust wrote: > On Wed, 2017-03-08 at 11:29 -0500, Jeff Layton wrote: > > If launder_page fails, then we hit a problem writing back some inode > > data. Ensure that we communicate that fact in a subsequent fsync > > since > > another task could still

Re: [PATCH v2 6/9] mm: set mapping error when launder_pages fails

2017-03-08 Thread Jeff Layton
On Wed, 2017-03-08 at 18:01 +, Trond Myklebust wrote: > On Wed, 2017-03-08 at 11:29 -0500, Jeff Layton wrote: > > If launder_page fails, then we hit a problem writing back some inode > > data. Ensure that we communicate that fact in a subsequent fsync > > since > > another task could still

Re: [PATCH v2 6/9] mm: set mapping error when launder_pages fails

2017-03-08 Thread Trond Myklebust
On Wed, 2017-03-08 at 11:29 -0500, Jeff Layton wrote: > If launder_page fails, then we hit a problem writing back some inode > data. Ensure that we communicate that fact in a subsequent fsync > since > another task could still have it open for write. > > Signed-off-by: Jeff Layton

Re: [PATCH v2 6/9] mm: set mapping error when launder_pages fails

2017-03-08 Thread Trond Myklebust
On Wed, 2017-03-08 at 11:29 -0500, Jeff Layton wrote: > If launder_page fails, then we hit a problem writing back some inode > data. Ensure that we communicate that fact in a subsequent fsync > since > another task could still have it open for write. > > Signed-off-by: Jeff Layton > --- >  

[PATCH v2 6/9] mm: set mapping error when launder_pages fails

2017-03-08 Thread Jeff Layton
If launder_page fails, then we hit a problem writing back some inode data. Ensure that we communicate that fact in a subsequent fsync since another task could still have it open for write. Signed-off-by: Jeff Layton --- mm/truncate.c | 6 +- 1 file changed, 5

[PATCH v2 6/9] mm: set mapping error when launder_pages fails

2017-03-08 Thread Jeff Layton
If launder_page fails, then we hit a problem writing back some inode data. Ensure that we communicate that fact in a subsequent fsync since another task could still have it open for write. Signed-off-by: Jeff Layton --- mm/truncate.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-)