Do not require write-access for fsync
* fsync doesn't modify the file. It doesn't make sense to require write-access. * This matches what ~all other systems do. At least Linux, macOS, and NetBSD.
This commit is contained in:
parent
3aed0aa641
commit
39ab0f4836
1 changed files with 0 additions and 7 deletions
|
@ -55,13 +55,6 @@ int file_fsync(FAR struct file *filep)
|
|||
{
|
||||
struct inode *inode;
|
||||
|
||||
/* Was this file opened for write access? */
|
||||
|
||||
if ((filep->f_oflags & O_WROK) == 0)
|
||||
{
|
||||
return -EBADF;
|
||||
}
|
||||
|
||||
/* Is this inode a registered mountpoint? Does it support the
|
||||
* sync operations may be relevant to device drivers but only
|
||||
* the mountpoint operations vtable contains a sync method.
|
||||
|
|
Loading…
Reference in a new issue