On Tue, 16 Jan 2007, Arjan van de Ven wrote: > On Tue, 2007-01-16 at 21:26 +0100, Bodo Eggert wrote: > > Helge Hafting <[EMAIL PROTECTED]> wrote: > > > Michael Tokarev wrote:
> > >> 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 ? > > > > Suspend O_DIRECT access while non-O_DIRECT-fds are open, fdatasync on close? > > .. then any user can impact the operation, performance and reliability > of the database application of another user... sounds like plugging one > hole by making a bigger hole ;) Don't allow other users to access your raw database files then, and if backup kicks in, pausing the database would DTRT for integrety of the backup. For other applications, paused O_DIRECT may very well be a problem, but I can't think of one right now. -- Logic: The art of being wrong with confidence... - 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/
