mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Peter Staubach <staubach@redhat.com>
Cc: Kenny Simpson <theonetruekenny@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: another nfs puzzle
Date: Wed, 07 Dec 2005 10:41:57 -0500	[thread overview]
Message-ID: <1133970117.27373.53.camel@lade.trondhjem.org> (raw)
In-Reply-To: <4397011E.9010703@redhat.com>

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.

Cheers,
  Trond


  reply	other threads:[~2005-12-07 15:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-06 22:04 Kenny Simpson
2005-12-07  3:24 ` Trond Myklebust
2005-12-07 14:50   ` Kenny Simpson
2005-12-07 14:01 ` Peter Staubach
2005-12-07 14:11   ` Trond Myklebust
2005-12-07 14:18     ` Peter Staubach
2005-12-07 14:34       ` Trond Myklebust
2005-12-07 15:34         ` Peter Staubach
2005-12-07 15:41           ` Trond Myklebust [this message]
2005-12-07 15:56             ` Peter Staubach
2005-12-07 16:09               ` Trond Myklebust
2005-12-07 16:39                 ` Peter Staubach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1133970117.27373.53.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=staubach@redhat.com \
    --cc=theonetruekenny@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®