From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <77067f767af078de8a6313db33e64977@rei2.9hal>
Date: Mon,  2 Apr 2012 21:52:31 +0200
From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
In-Reply-To: <f82299da5b030d9ca8914dae96b0ea5d@sp.nv>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] SSHv2
Topicbox-Message-UUID: 74b6365a-ead7-11e9-9d60-3106f5b1d025

can reproduce it here. the problem is 9fronts implementaiton
of ioprocs. instead of posting notes, we added a "interrupt" and
"nointerrupt" ctl messages to /proc/n/ctl that interrupts without
posting a note.

the problem was that notes could be scheduled before we even did
the syscall making them unreliable.

this mechanism simplified the ioproc implementation quite a lot,
but relied on the fact that one can open /proc/n/ctl of the
ioproc().

this breaks because nfactotum makes its ctl file readonly so it
can't be killed.

fortunately, it doesnt use iointerrupt() at all so we could just
ignore the failing open of /proc/n/ctl in the case of factotum.

--
cinap