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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Chris Friesen <[email protected]> wrote:
>
> Andrew Morton wrote:
> > Chris Friesen <[email protected]> wrote:
> 
> >> Would a patch that makes it 
> >>just return successfully without doing anything be accepted?
> > 
> > 
> > yup.
> 
> Currently tmpfs reuses the simple_dir_operations from libfs.c.
> 
> Would it make sense to add the empty fsync() function there, and have 
> all other users pick it up as well?  Is this likely to break stuff?

Isn't simple_sync_file() suitable?

-
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/

[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]
  Powered by Linux