On Thu, 2018-05-31 at 07:29 -0400, Jeff Layton wrote:
> From: Jeff Layton
>
> v2: don't modify sync_fs op prototype, handle errors at vfs layer
>
> The syncfs system call returns an int error code, but in general it does
> not return errors when an inode fails writeback. It will return an error
On Thu, 2018-05-31 at 07:29 -0400, Jeff Layton wrote:
> From: Jeff Layton
>
> v2: don't modify sync_fs op prototype, handle errors at vfs layer
>
> The syncfs system call returns an int error code, but in general it does
> not return errors when an inode fails writeback. It will return an error
From: Jeff Layton
v2: don't modify sync_fs op prototype, handle errors at vfs layer
The syncfs system call returns an int error code, but in general it does
not return errors when an inode fails writeback. It will return an error
if __sync_blockdev fails, but that's not useful on non-block
From: Jeff Layton
v2: don't modify sync_fs op prototype, handle errors at vfs layer
The syncfs system call returns an int error code, but in general it does
not return errors when an inode fails writeback. It will return an error
if __sync_blockdev fails, but that's not useful on non-block
4 matches
Mail list logo
