Messages in this thread | | | Date | Fri, 05 Jan 2007 14:49:42 +0300 | From | Michael Tokarev <> | Subject | Re: open(O_DIRECT) on a tmpfs? |
| |
Hugh Dickins wrote: > On Thu, 4 Jan 2007, Michael Tokarev wrote: >> I wonder why open() with O_DIRECT (for example) bit set is >> disallowed on a tmpfs (again, for example) filesystem, >> returning EINVAL. [] > p.s. You said "O_DIRECT (for example)" - what other open > flag do you think tmpfs should support which it does not?
Well. Somehow I was under an impression O_SYNC behaves the same as O_DIRECT on a tmpfs. But I was wrong - tmpfs permits O_SYNC opens just fine. Strange thing to do having in mind its behaviour with O_DIRECT - to me it's inconsistent ;) But that's it - looks like only O_DIRECT is "mishandled" (which is not a big deal obviously).
Thanks for your time!
/mjt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |