All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Arne Georg Gleditsch <argggh@dolphinics.no>
Cc: Florian Attenberger <valdyn@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.21.5 june 30th to july 1st date hang?
Date: Tue, 03 Jul 2007 15:28:36 -0400	[thread overview]
Message-ID: <468AA364.2010000@nortel.com> (raw)
In-Reply-To: <87d4z97bks.fsf@pelargir.dolphinics.no>

Arne Georg Gleditsch wrote:

> An interesting exercise might be to
> code up a small program to call adjtimex with timex.status |= STA_INS,
> to see if this can trigger the problem.

Setting the date to just before midnight June 30 UTC and then running the 
following as root triggered the crash on a modified 2.6.10.  Anyone see anything 
wrong with the code below, or is this a valid indication of a bug in the leap 
second code?

Chris


#include <sys/timex.h>
#include <stdio.h>
#include <errno.h>

struct timex buf;
int main(void)
{
	int rc = adjtimex(&buf);
	printf("initial status: 0x%x\n", buf.status);
	buf.status |= STA_INS;
	buf.modes = ADJ_STATUS;
	rc = adjtimex(&buf);
	if (rc == -1) {
		printf("unable to set status: %m\n");
		return -1;
	} else
		printf("rc: %d\n", rc);
	printf("final status: 0x%x\n", buf.status);
	return 0;
}

  parent reply	other threads:[~2007-07-03 19:28 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03 12:44 2.6.21.5 june 30th to july 1st date hang? Fortier,Vincent [Montreal]
2007-07-03 12:55 ` Fortier,Vincent [Montreal]
2007-07-03 13:05 ` Clemens Koller
2007-07-03 14:51   ` Fortier,Vincent [Montreal]
2007-07-03 13:56 ` Uli Luckas
2007-07-03 13:59 ` Florian Attenberger
2007-07-03 14:20   ` Arne Georg Gleditsch
2007-07-03 15:02     ` Florian Attenberger
2007-07-03 15:26       ` Arne Georg Gleditsch
2007-07-03 15:36         ` Fortier,Vincent [Montreal]
2007-07-03 17:19           ` Dave Jones
2007-07-03 19:28         ` Chris Friesen [this message]
2007-07-03 21:02           ` Chris Friesen
2007-07-03 21:02           ` Chuck Ebbert
2007-07-04  1:06             ` Fortier,Vincent [Montreal]
2007-07-04  8:56             ` Uli Luckas
2007-07-04 16:53               ` Chris Wright
2007-07-05 14:13                 ` Clemens Koller
2007-07-05 17:48                   ` Chris Friesen
2007-07-05 18:34                     ` Clemens Koller
2007-07-05 20:10                     ` Thomas Gleixner
2007-07-05 21:02                       ` Chris Friesen
2007-07-05 21:17                         ` Thomas Gleixner
2007-07-05 22:28                     ` Ernie Petrides
2007-07-05 22:49                       ` Chris Friesen
2007-07-05 23:12                         ` Ernie Petrides
2007-07-05 23:45                           ` Chris Friesen
2007-07-06  5:16                             ` Thomas Gleixner
2007-07-06  5:17                           ` Thomas Gleixner
2007-07-06 15:47                             ` Chris Friesen
2007-07-06 20:03                             ` Ernie Petrides
2007-07-03 15:59 ` Chris Friesen
2007-07-03 16:00   ` Fortier,Vincent [Montreal]
2007-07-03 16:03     ` Chris Friesen
2007-07-03 17:28       ` Chris Friesen

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=468AA364.2010000@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=argggh@dolphinics.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=valdyn@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.