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

The man page for fsync() suggests that it is necessary to call it on the directory fd.

However, in the case of tmpfs, fsync() on the file completes, but on the directory it returns -1 with errno==EINVAL.

Is there any particular reason for this? Would a patch that makes it just return successfully without doing anything be accepted?

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/

---

• Follow-Ups:
  • Re: why does fsync() on a tmpfs directory give EINVAL?
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: [Ext2-devel] Re: [RFD] FS behavior (I/O failure) in kernel summit
• Next by Date: Re: 2.6.12-rc6-mm1 & 2K lun testing
• Previous by thread: Oops calling sysfs_create_link() from pci_probe()
• Next by thread: Re: why does fsync() on a tmpfs directory give EINVAL?
• 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]