Path: utzoo!mnetor!uunet!husc6!think!ames!rutgers!ukma!gatech!galbp!bing
From: bing@galbp.LBP.HARRIS.COM (Bing Bang)
Newsgroups: comp.os.minix
Subject: Re: Deadlock in Minix
Message-ID: <3105@galbp.LBP.HARRIS.COM>
Date: 18 Dec 87 22:04:32 GMT
References: <1064@kulcs.UUCP>
Reply-To: bing@galbp.UUCP (Bing Bang)
Organization: Harris/Lanier, Atlanta, GA
Lines: 23
Keywords: deadlock, sys_call bug

In article <1064@kulcs.UUCP> bart@kulcs.UUCP (Bart De Decker) writes:
>
>I added the following code to kernel/proc.c.
>It detects a deadlock that arises when two processes (or tasks) try to send
>each other a message at the same time.
>
[dif code]
>
>Not really a solution, but it shows clearly the deadlock problem  ...
>
>-- Bart

long ago, i posted changes to fs and the kernel to solve this problem.
it involved creating a que for messages, so that the sender is never
blocked by not being able to send. of course the messages must be copied
to a system resourced message structure so that the sender can safely re-
use his message structure.


-- 
Bing H. Bang           +----------------------------------------------------+
Harris/Lanier          |MSDOS and OS/2 (whenever it gets here): just say no.|
Atlanta GA             +----------------------------------------------------+