From: Alexander Viro <viro@math.psu.edu>
To: Manfred Spraul <manfreds@colorfullife.com>
Cc: linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: execve-question
Date: Sun, 10 Oct 1999 12:12:24 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.10.9910101207500.16317-100000@weyl.math.psu.edu> (raw)
In-Reply-To: <3800B13E.655140FE@colorfullife.com>
On Sun, 10 Oct 1999, Manfred Spraul wrote:
> what happens / should happen if I call execve() in a multi-threaded
> application?
>
> I don't see that the mm structure is copied, and obviously noone
> acquires the mm->mmap_sem.
Check fs/exec.c::exec_mmap(). mmap_sem is _not_ needed here. We are not
copying the mm - we are creating new one (exec drops all mappings). For
$DEITY sake, stop applying band-aids.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
prev parent reply other threads:[~1999-10-10 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-10 15:31 execve-question Manfred Spraul
1999-10-10 16:12 ` Alexander Viro [this message]
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.GSO.4.10.9910101207500.16317-100000@weyl.math.psu.edu \
--to=viro@math.psu.edu \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=manfreds@colorfullife.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