9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] devproc noteid changing for none
Date: Thu,  2 Jan 2014 17:47:46 -0500	[thread overview]
Message-ID: <6095eb4244b068d7bcdaec4ed6a65f2a@mikro> (raw)
In-Reply-To: <14d36fdb195faa18bbf2f6b28553cdaa@mikro>

On Thu Jan  2 17:32:08 EST 2014, quanstro@quanstro.net wrote:
> On Thu Jan  2 16:55:59 EST 2014, cinap_lenrek@felloff.net wrote:
> > i was investigating all callers of postnote() for bugs that could
> > lead to spurious notes like the alarm race i described before. btw
> > this has been fixed too. the key is to recheck p->alarm while holding
> > p->debug qlock. once you have it, the process cannot exit under you.
>
> cool.  if that's the protocol, doesn't the debug lock need to be held whenever
> up->alarm is modified?

checkalarms will hang during rollover.  suppose sys->ticks = 1<<31,
then (long)((1<<31) - 0) = -2147483648.  this will stay negative for a
2147483648/HZ seconds.

i think this is necessary:

void
checkalarms(void)
{
	Proc *p;
	ulong now;

	p = alarms.head;
	now = sys->ticks;

	if(p != nil)
	if(p->alarm == 0 || (long)(now - p->alarm) >= 0)
		wakeup(&alarmr);
}

- erik



  reply	other threads:[~2014-01-02 22:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02 21:17 cinap_lenrek
2014-01-02 21:22 ` erik quanstrom
2014-01-02 21:29   ` cinap_lenrek
2014-01-02 21:32   ` cinap_lenrek
2014-01-02 21:35     ` erik quanstrom
2014-01-02 21:41       ` cinap_lenrek
2014-01-02 21:43       ` erik quanstrom
2014-01-02 21:55         ` cinap_lenrek
2014-01-02 22:31           ` erik quanstrom
2014-01-02 22:47             ` erik quanstrom [this message]
2014-01-02 22:56               ` cinap_lenrek
2014-01-02 22:53             ` cinap_lenrek
2014-01-02 22:57               ` erik quanstrom
2014-01-02 23:01                 ` cinap_lenrek
2014-01-02 23:04                   ` erik quanstrom
2014-01-02 23:05                 ` cinap_lenrek
2014-01-02 23:09                 ` cinap_lenrek
2014-01-02 23:17                   ` cinap_lenrek
2014-01-02 23:28                     ` erik quanstrom
2014-01-03  0:23                       ` erik quanstrom
2014-01-03  0:32                         ` cinap_lenrek
2014-01-03  1:16                           ` erik quanstrom
2014-01-03  1:23                             ` cinap_lenrek
2014-01-03  1:31                               ` erik quanstrom

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=6095eb4244b068d7bcdaec4ed6a65f2a@mikro \
    --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).