Messages in this thread | | | Date | Mon, 15 Jan 2007 13:11:21 +0100 | From | Helge Hafting <> | Subject | Re: O_DIRECT question |
| |
Michael Tokarev wrote: > Chris Mason wrote: > [] > >> I recently spent some time trying to integrate O_DIRECT locking with >> page cache locking. The basic theory is that instead of using >> semaphores for solving O_DIRECT vs buffered races, you put something >> into the radix tree (I call it a placeholder) to keep the page cache >> users out, and lock any existing pages that are present. >> > > But seriously - what about just disallowing non-O_DIRECT opens together > with O_DIRECT ones ? > Please do not create a new local DOS attack. I open some important file, say /etc/resolv.conf with O_DIRECT and just sit on the open handle. Now nobody else can open that file because it is "busy" with O_DIRECT ?
Helge Hafting - 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/
| |