From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: select, jiffies, and SIGALRM
Date: Wed, 13 Oct 2004 21:28:26 -0600 [thread overview]
Message-ID: <005d01c4b19d$de6e2a00$6601a8c0@northbrook> (raw)
In-Reply-To: fa.g84jc6u.73qi0a@ifi.uio.no
I see calls to getitimer, so I'm assuming it's also using setitimer. SIGALRM
is what you get when those timers go off - if it's not handling that, that's
a bug, but presumably the timer is in there for a reason..
----- Original Message -----
From: "Vx Glenn" <VxGlenn@gmail.com>
Newsgroups: fa.linux.kernel
To: <linux-net@vger.kernel.org>; <linux-kernel@vger.kernel.org>
Sent: Wednesday, October 13, 2004 10:13 AM
Subject: select, jiffies, and SIGALRM
> Hi all,
>
> I am seeing an issue relating to the jiffies counter wrapping around
> at 0x7FFFFFFF.
>
> This is a legacy application, and when it runs on 32-bit Unix-Like
> OS's, the application silently dies without leaving core after 248
> days.
>
> I was able to manipulate the jiffies counter and run the application.
> I was able to reproduce the problem. I captured an strace log, and I
> see that SIGALRM (alarm clock) is raised after select times out
> (because of no data).
>
> I can add a signal handler to intercept the SIGALRM. But my question
> is, why should the signal be raised?
>
> ---[ strace.log ]---
> select(1024, [3 4 5 6], NULL, NULL, {0, 320000}) = 0 (Timeout)
> getitimer(ITIMER_REAL, {it_interval={2147157, 520}, it_value={0, 684895}})
> = 0
> adjtimex({modes=32769, offset=0, freq=0, maxerror=16384000,
> esterror=16384000, status=64, constant=2, precision=1,
> tolerance=33554432, time={1097551596, 43475}}) = 5
> getitimer(ITIMER_REAL, {it_interval={2147157, 520}, it_value={0, 684895}})
> = 0
> select(1024, [3 4 5 6], NULL, NULL, {1, 0}) = ? ERESTARTNOHAND (To be
> restarted)
> --- SIGALRM (Alarm clock) @ 0 (0) ---
> Process 4881 detached
> ---[ eof strace.log ]---
>
>
> Anyone have any ideas?
>
>
> --
> You're not your Job;
> You're not the contents of your wallet.
> You're the all singing all dancing crap of the world
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2004-10-14 3:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.g84jc6u.73qi0a@ifi.uio.no>
2004-10-14 3:28 ` Robert Hancock [this message]
2004-10-14 17:35 ` select, jiffies, and SIGALRM Vx Glenn
[not found] <fa.j10pg5k.1q08a2k@ifi.uio.no>
[not found] ` <fa.je28id0.1i0sfq4@ifi.uio.no>
2004-10-15 1:23 ` Robert Hancock
2004-10-13 16:11 Vx Glenn
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='005d01c4b19d$de6e2a00$6601a8c0@northbrook' \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
/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.