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

Chris Friesen <[email protected]> wrote:
>
> 
> The man page for fsync() suggests that it is necessary to call it on the 
> directory fd.

yup.

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

bad.

> Is there any particular reason for this?

nope.

>  Would a patch that makes it 
> just return successfully without doing anything be accepted?

yup.
-
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: Chris Friesen <[email protected]>

• References:
  • why does fsync() on a tmpfs directory give EINVAL?
    • From: Chris Friesen <[email protected]>

• Prev by Date: Re: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
• Next by Date: Re: [resend][PATCH] avoid signed vs unsigned comparison in efi_range_is_wc()
• Previous by thread: why does fsync() on a tmpfs directory give EINVAL?
• 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]