From: ebiederm+eric@ccr.net (Eric W. Biederman)
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: vfork & co bugfix
Date: 10 Jan 1999 15:34:46 -0600 [thread overview]
Message-ID: <m1u2xy6ccp.fsf@flinx.ccr.net> (raw)
In-Reply-To: Linus Torvalds's message of "Sun, 10 Jan 1999 10:04:25 -0800 (PST)"
>>>>> "LT" == Linus Torvalds <torvalds@transmeta.com> writes:
LT> On 10 Jan 1999, Eric W. Biederman wrote:
>>
>> Looking at vfork in 2.2.0-pre6 I was struck by how badly
>> looking at current, (to release a process) hacks up mmput.
>>
>> It took a little while but eventually a case where
>> this really goes wrong.
LT> Note that the pre6 version has a number of cases where it can really screw
LT> up, don't even look at them too closely. I think I've fixed them all - it
LT> was really simple, but there was a few things I hadn't originally thought
LT> of.
LT> I'll make a pre7 once I've verified that the recursive semaphores work at
LT> least to some degree, could you please take a look at that one?
Will do.
The messing up of segments, and the ldt is much older than pre6 though.
The vfork release semaphore code just happened to make about the same assumption,
so I fixed them both at the same time.
Eric
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1999-01-10 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-10 6:48 Eric W. Biederman
1999-01-10 18:04 ` Linus Torvalds
1999-01-10 21:34 ` Eric W. Biederman [this message]
1999-01-11 4:32 ` Eric W. Biederman
1999-01-11 6:35 ` Linus Torvalds
1999-01-11 6:59 ` Eric W. Biederman
1999-01-11 7:31 ` Linus Torvalds
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=m1u2xy6ccp.fsf@flinx.ccr.net \
--to=ebiederm+eric@ccr.net \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.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