From 71a07158a4fac4aadcc32703b0701fb894a94aa4 Mon Sep 17 00:00:00 2001 From: Charles Manning Date: Fri, 13 Mar 2020 12:26:37 +1300 Subject: [PATCH] rtems_yaffs: Remove unnecessary flushing of symlink Flushing only has meaning on regular files which have cached data. Symlinks do not have any cached data, therefore flushing has no purpose. Remove. Signed-off-by: Charles Manning --- rtems/rtems_yaffs.c | 8 -------- 1 file changed, 8 deletions(-) diff --git a/rtems/rtems_yaffs.c b/rtems/rtems_yaffs.c index 8ee0b89..4611320 100644 --- a/rtems/rtems_yaffs.c +++ b/rtems/rtems_yaffs.c @@ -684,14 +684,6 @@ static int ryfs_symlink(const rtems_filesystem_location_info_t *parent_loc, geteuid(), getegid(), target); if (created_link != NULL) { - // In RTEMS VFS, there is no filesytem-wide sync(), only per-file - // flushes. Filesystem-wide sync is implemented by looping over all of - // the open files and individually fsync()ing them. That's part of why - // every close() in RTEMS-yaffs is accompanied by an implicit fsync(). - // There is no such close() call associated with the symlink's creation, - // since it wasn't created via open(). Therefore, flush it immediately - // instead. - yaffs_flush_file(created_link, 0, 0, 0); ret = 0; } else { errno = EINVAL; -- 2.30.2