From: Hugh Dickins <hugh@veritas.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Smarduch Mario-CMS063 <CMS063@motorola.com>,
linux-kernel@vger.kernel.org
Subject: Re: Multi-Threaded fork() correctness on Linux 2.4 & 2.6
Date: Mon, 19 Sep 2005 22:30:32 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.61.0509192227530.26271@goblin.wat.veritas.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0509191327160.2553@g5.osdl.org>
On Mon, 19 Sep 2005, Linus Torvalds wrote:
>
> Hmm. But we do hold the mmap_sem for writing, and we flush before we
> release it, so it should still be ok. The page fault case needs to get it
> for reading anyway.
>
> Yeah, the page_table_lock might make more sense, but I think the mmap_sem
> thing works equally well.
Yes, you're both ahead of me: thank you for working that out: no issue.
Hugh
next prev parent reply other threads:[~2005-09-19 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 16:24 Smarduch Mario-CMS063
2005-09-19 18:42 ` Hugh Dickins
2005-09-19 19:24 ` Linus Torvalds
2005-09-19 20:14 ` Hugh Dickins
2005-09-19 20:39 ` Linus Torvalds
2005-09-19 21:30 ` Hugh Dickins [this message]
2005-09-19 20:21 Smarduch Mario-CMS063
2005-09-19 20:47 ` Linus Torvalds
2005-09-19 20:34 Smarduch Mario-CMS063
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.0509192227530.26271@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=CMS063@motorola.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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®