Re: why does fsync() on a tmpfs directory give EINVAL?

Hugh Dickins wrote:

No need to check the list: any filesystem using simple_dir_operations
is using dcache_readdir, which implies there's no storage to be synced.
And we all agree that success is a more helpful retval than -EINVAL
when there's nothing for fsync to do.  Here's a patch if you haven't
done it already....

Thanks for the input. I wasn't positive the change would be benign, soI was waiting for the discussion to resolve itself.


Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- why does fsync() on a tmpfs directory give EINVAL?
  - From: Chris Friesen <[email protected]>
- Re: why does fsync() on a tmpfs directory give EINVAL?
  - From: Andrew Morton <[email protected]>
- Re: why does fsync() on a tmpfs directory give EINVAL?
  - From: Chris Friesen <[email protected]>
- Re: why does fsync() on a tmpfs directory give EINVAL?
  - From: Andrew Morton <[email protected]>
- Re: why does fsync() on a tmpfs directory give EINVAL?
  - From: Chris Friesen <[email protected]>
- Re: why does fsync() on a tmpfs directory give EINVAL?
  - From: Andrew Morton <[email protected]>
- Re: why does fsync() on a tmpfs directory give EINVAL?
  - From: Hugh Dickins <[email protected]>

Prev by Date: Re: [patch] Real-Time Preemption, -RT-2.6.12-rc6-V0.7.48-00
Next by Date: Kernel eats argument=
Previous by thread: Re: why does fsync() on a tmpfs directory give EINVAL?
Next by thread: [resend][PATCH] avoid signed vs unsigned comparison in efi_range_is_wc()
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]