Trond Myklebust wrote:
On Wed, 2005-12-07 at 10:34 -0500, Peter Staubach wrote:
This seems like a dangerous enough area that denying mmap on a file which
has been opened with O_DIRECT by any process and denying open(O_DIRECT)
on a file which has been mmap'd would be a good thing. These things are
easy enough to keep track of, so it shouldn't be too hard to implement.
That would be a recipe for DOSes as it would allow one process to block
another just by opening a file. I'd really not like to see my database
crash just because some obscure monitoring program happens to use mmap()
to browse the file.
I wouldn't think that a database would be a problem since it is opened early
and then stays open. However, point granted. There are tools around, lsof
and such, which would be handy for diagnosing such a situation though.
I do know of other operating systems which do implement the semantics that I
have suggested and I don't think that they are concerned or have been
notified
that these semantics for a problem. These semantics are used because the
kernel itself can not even guarantee that the data that it is caching is
valid,
without lots of synchronization which may tend to reduce performance.
Thanx...
ps
-
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]
