From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: Re: [9fans] SSHv2
Date: Mon, 2 Apr 2012 21:52:31 +0200 [thread overview]
Message-ID: <77067f767af078de8a6313db33e64977@rei2.9hal> (raw)
In-Reply-To: <f82299da5b030d9ca8914dae96b0ea5d@sp.nv>
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
next prev parent reply other threads:[~2012-04-02 19:52 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 2:10 blstuart
2012-03-30 1:26 ` cinap_lenrek
2012-03-30 3:15 ` Bruce Ellis
2012-03-30 2:14 ` andrey mirtchovski
2012-03-30 4:21 ` Lucio De Re
2012-03-30 4:49 ` Lucio De Re
2012-03-30 6:07 ` David du Colombier
2012-03-30 8:11 ` Lucio De Re
2012-03-30 13:32 ` erik quanstrom
2012-03-30 5:48 ` Jeff Sickel
2012-03-30 8:10 ` steve
2012-03-30 9:19 ` Richard Miller
2012-03-30 10:43 ` Yaroslav
2012-03-30 12:48 ` blstuart
2012-03-30 12:56 ` erik quanstrom
2012-04-02 20:50 ` Richard Miller
2012-04-02 20:08 ` Richard Miller
2012-04-03 2:27 ` Lyndon Nerenberg
2012-04-03 2:31 ` Lyndon Nerenberg
2012-04-23 8:40 ` rhoyerboat
2012-04-23 20:55 ` Richard Miller
2012-04-25 12:47 ` David Leimbach
2012-04-25 15:25 ` andy zerger
2012-03-30 10:48 ` Yaroslav
2012-03-30 11:00 ` Lucio De Re
2012-03-30 13:03 ` erik quanstrom
2012-03-30 14:19 ` Charles Forsyth
2012-03-30 12:50 ` blstuart
2012-03-30 10:49 ` Yaroslav
2012-03-30 11:17 ` Yaroslav
2012-03-30 13:01 ` blstuart
[not found] ` <CAG3N4d-1A3VzHsyxSdiRG8-Q9NtYoe8xGUi6B9AVg3inR0Eq_Q@mail.gmail.c>
2012-03-30 12:54 ` erik quanstrom
2012-03-30 13:36 ` erik quanstrom
2012-03-30 13:55 ` Yaroslav
2012-03-30 13:59 ` Lucio De Re
2012-03-30 13:59 ` Lucio De Re
2012-03-30 14:44 ` erik quanstrom
2012-04-02 14:27 ` sl
2012-04-02 14:29 ` erik quanstrom
2012-04-02 14:39 ` erik quanstrom
2012-04-02 16:12 ` Brian L. Stuart
2012-04-02 16:32 ` sl
2012-04-02 16:53 ` sl
2012-04-02 17:21 ` Brian L. Stuart
2012-04-02 17:57 ` sl
2012-04-02 19:52 ` cinap_lenrek [this message]
2012-04-02 16:56 ` Brian L. Stuart
2012-04-02 16:27 ` Brian L. Stuart
2012-04-02 16:33 ` sl
2012-04-02 16:44 ` Brian L. Stuart
2012-04-23 1:11 ` andy zerger
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=77067f767af078de8a6313db33e64977@rei2.9hal \
--to=cinap_lenrek@gmx.de \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).