From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Mon, 30 Dec 2013 12:43:21 -0500
To: 9fans@9fans.net
Message-ID: <3377fb7342a3ff404eae1ba724f11130@mikro>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] 9front sleep interrupted in kproc?
Topicbox-Message-UUID: a9ba0b8c-ead8-11e9-9d60-3106f5b1d025

not sure where to send this comment.

i think this patch misunderstands the situation.  the patch
claims that some code is wrong because sleep in a kproc might
get interrupted.

	http://code.google.com/p/plan9front/source/detail?r=3864ff1fe83f254622e6f10925f53df62255336d

this diff highlights the issue

	http://code.google.com/p/plan9front/source/diff?spec=svn3864ff1fe83f254622e6f10925f53df62255336d&r=3864ff1fe83f254622e6f10925f53df62255336d&format=side&path=/sys/src/9/port/alarm.c

the crux of the matter is when sleep might be interrupted.  sleep
is interrupted iff process received a note.

since kprocs don't get notes (it's an error to write to the note file),
sleep in a kproc can't get interrupted.  this code will never fire.

- erik