public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "P at draigBrady dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/13567] New: overflow in emulated timer_settime() on Linux/HPPA at least
Date: Thu, 05 Jan 2012 21:32:00 -0000	[thread overview]
Message-ID: <bug-13567-131@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=13567

             Bug #: 13567
           Summary: overflow in emulated timer_settime() on Linux/HPPA at
                    least
           Product: glibc
           Version: 2.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper.fsp@gmail.com
        ReportedBy: P@draigBrady.com
    Classification: Unclassified


Created attachment 6150
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6150
An strace of the problematic timeout run

When testing recent coreutils releases on parisc linux, it was noticed
that timer_settime($large_num) would cause the timer
to immediately fire when $large_num spanned the 2038 boundary.
This function is used by the `timeout` utility.

Seems to me that time_t is overflowing,
and being interpreted as a negative number.
Note time_t is signed 32-bit on this platform.

$ uname -srm
Linux 2.6.22.19 parisc

$ /lib/libc.so.6 GNU C Library stable release version 2.7, by Roland McGrath et
al.
Copyright (C) 2007 Free Software Foundation, Inc.
...
Compiled by GNU CC version 4.3.2.
Compiled on a Linux >>2.6.32-5-parisc<< system on 2011-01-07.
Available extensions:
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        linuxthreads-0.10 by Xavier Leroy
        libthread_db work sponsored by Alpha Processor Inc
        Support for some architectures added on, not maintained in glibc core.
        BIND-8.2.3-T5B

$ grep HAVE_TIMER_SETTIME ../lib/config.h
#define HAVE_TIMER_SETTIME 1

$ nm timeout|grep ' U timer'
         U timer_create@@GLIBC_2.2
         U timer_delete@@GLIBC_2.2
         U timer_settime@@GLIBC_2.2

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-01-05 21:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 21:32 P at draigBrady dot com [this message]
2012-01-05 23:39 ` [Bug ports/13567] " schwab@linux-m68k.org
2012-02-15 22:34 ` jsm28 at gcc dot gnu.org
2012-02-16  1:17 ` carlos at systemhalted dot org
2012-02-19  2:11 ` jsm28 at gcc dot gnu.org
2014-05-14 17:03 ` [Bug libc/13567] [hppa] " jsm28 at gcc dot gnu.org
2014-06-27 11:15 ` fweimer at redhat dot com
2015-08-27 22:07 ` [Bug librt/13567] " jsm28 at gcc dot gnu.org
2022-06-10  0:45 ` sam at gentoo dot org

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=bug-13567-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).