From: Hugh Dickins <hugh@veritas.com>
To: Gleb Natapov <glebn@voltaire.com>
Cc: "Michael S. Tsirkin" <mst@mellanox.co.il>,
Roland Dreier <roland@topspin.com>,
linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: [openib-general] Re: [PATCH repost] PROT_DONTCOPY: ifiniband uverbs fork support
Date: Wed, 10 Aug 2005 16:27:31 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.61.0508101623480.4525@goblin.wat.veritas.com> (raw)
In-Reply-To: <20050810132611.GP16361@minantech.com>
On Wed, 10 Aug 2005, Gleb Natapov wrote:
> On Wed, Aug 10, 2005 at 02:22:40PM +0100, Hugh Dickins wrote:
> >
> > Your stack example is a good one: if we end up setting VM_DONTCOPY on
> > the user stack, then I don't think fork's child will get very far without
> > hitting a SIGSEGV.
>
> I know, but I prefer child SIGSEGV than silent data corruption.
Most people will share your preference, but neither is satisfactory.
> In most cases child will exec immediately after fork so no problem
> in this case.
In most(?) cases it won't even be able to exec before the SIGSEGV.
Hugh
next prev parent reply other threads:[~2005-08-10 15:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 16:55 [PATCH] " Michael S. Tsirkin
2005-07-25 17:19 ` [PATCH repost] PROT_DONTCOPY: ifiniband uverbs " Michael S. Tsirkin
2005-07-26 12:30 ` Hugh Dickins
2005-07-26 13:35 ` Michael S. Tsirkin
2005-08-09 18:13 ` Hugh Dickins
2005-08-10 8:30 ` Michael S. Tsirkin
2005-08-10 8:39 ` [openib-general] " Gleb Natapov
2005-08-10 13:22 ` Hugh Dickins
2005-08-10 13:26 ` Gleb Natapov
2005-08-10 15:27 ` Hugh Dickins [this message]
2005-08-11 8:02 ` Gleb Natapov
2005-08-11 14:04 ` Hugh Dickins
2005-08-11 14:07 ` Gleb Natapov
2005-08-11 14:17 ` Hugh Dickins
2005-08-11 14:11 ` Michael S. Tsirkin
2005-08-15 16:37 ` Bill Jordan
2005-08-16 7:52 ` Gleb Natapov
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=Pine.LNX.4.61.0508101623480.4525@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=glebn@voltaire.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@mellanox.co.il \
--cc=openib-general@openib.org \
--cc=roland@topspin.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®