Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!udel!mmdf From: Postmaster@locke.bitnet (PMDF Mail Server) Newsgroups: comp.os.minix Subject: Undeliverable mail Message-ID: <858@louie.udel.EDU> Date: 19 Dec 87 16:58:56 GMT Sender: mmdf@udel.EDU Lines: 43 The message could not be delivered to: Addressee: MINIX Reason: %MAIL-E, no such user MINIX at node LOCKE ---------------------------------------- Received: from JNET-DAEMON by locke.hs.washington.edu; Sat, 19 Dec 87 08:55 PST Received: From NDSUVM1(MAILER) by UWALOCKE with RSCS id 3692 for MINIX@UWALOCKE; Sat, 19 Dec 87 08:55 PST Received: by NDSUVM1 (Mailer X1.24) id 3641; Sat, 19 Dec 87 10:52:54 CST Date: 18 Dec 87 22:04:32 GMT From: Bing Bang Subject: Re: Deadlock in Minix Sender: Minix operating system To: Local Redistribution Reply-to: INFO-MINIX@UDEL.edu Comments: To: info-minix@UDEL.EDU 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 +----------------------------------------------------+