From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9front sleep interrupted in kproc?
Date: Mon, 30 Dec 2013 23:40:36 -0500 [thread overview]
Message-ID: <a904a257f1455cbd4fab9cf6ae3d19e4@brasstown.quanstro.net> (raw)
In-Reply-To: <20131231012446.GB10407@dinah>
On Mon Dec 30 20:26:47 EST 2013, ality@pbrane.org wrote:
> Anthony Martin <ality@pbrane.org> once said:
> > erik quanstrom <quanstro@quanstro.net> once said:
> > > 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.
> >
> > It looks like they can on 9front.
>
> Actually, this isn't just 9front. All of the network
> medium receive kprocs (e.g., etherread4) can be sent
> notes (only by the kernel, of course).
there are no calls to procalarm() outside of sysalarm (the alarm
system call) in either the official sources or 9atom (either the 64bit
or regular kernels).
if i've pulled correctly, 9front has one procalarm, and it's in the vesa code
with a waserror at the ready.
this patch addresses a problem that doesn't exist. it seems to imply
that notes can come to kprocs out of the blue. and i believe this is
not correct.
- erik
next prev parent reply other threads:[~2013-12-31 4:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 17:43 erik quanstrom
2013-12-31 1:06 ` Anthony Martin
2013-12-31 1:24 ` Anthony Martin
2013-12-31 4:40 ` erik quanstrom [this message]
2013-12-31 13:17 ` cinap_lenrek
2013-12-31 14:38 ` erik quanstrom
2013-12-31 10:55 ` Charles Forsyth
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=a904a257f1455cbd4fab9cf6ae3d19e4@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).