RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1099025 - ftime() possibly broken on ppc
Summary: ftime() possibly broken on ppc
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: glibc
Version: 6.5
Hardware: ppc
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: Carlos O'Donell
QA Contact: Arjun Shankar
URL:
Whiteboard:
Depends On: 1064945
Blocks: 1028285
TreeView+ depends on / blocked
 
Reported: 2014-05-19 10:42 UTC by Siddhesh Poyarekar
Modified: 2016-11-24 12:11 UTC (History)
8 users (show)

Fixed In Version: glibc-2.12-1.148.el6
Doc Type: Bug Fix
Doc Text:
This update fixes a bug in the gettimeofday VDSO implementation that resulted in gettimeofday returning an incorrect non-changing value, resulting in the ftime function returning the same non-changing value.
Clone Of: 1064945
Environment:
Last Closed: 2014-10-14 04:43:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:1391 0 normal SHIPPED_LIVE Moderate: glibc security, bug fix, and enhancement update 2014-10-14 01:11:04 UTC

Description Siddhesh Poyarekar 2014-05-19 10:42:57 UTC
+++ This bug was initially created as a clone of Bug #1064945 +++

Description of problem:
The configure script in the lrzsz package checks if the ftime() function works correctly and it seems this test hangs (infinite loop) on ppc in the current RHEL7 buildroot. It looks like the time field in the timeb structure doesn't change or the call now fails.

I've patched the lrzsz package to not try ftime(), but I thought this might be worth further investigation.

The last build that passed was with glibc-2.17-4.el7. 

Version-Release number of selected component (if applicable):
glibc-2.17-48.el7

How reproducible:
easily

Steps to Reproduce:
1. compile and run the c code below

Actual results:
hangs

Expected results:
runs for 10 seconds and returns 0.

Additional info:

The test code:

#include <sys/types.h>
#include <sys/timeb.h>
#include <stdio.h>
main ()
{
  struct timeb s, slast;
  int c = 0;
  ftime (&slast);
  while (c < 10)
    {
      ftime (&s);
      if (s.time < slast.time
      || (s.time == slast.time && s.millitm < slast.millitm)) {
      fprintf(stderr,"s: %ld, %ld, slast: %ld, %ld\n",
        s.time,s.millitm, slast.time,slast.millitm);
    exit (1);
        }
      if (s.time != slast.time)
    ++c;
      slast.time = s.time;
      slast.millitm = s.millitm;
    }
  exit (0);
}

Comment 1 Siddhesh Poyarekar 2014-05-19 10:47:49 UTC
This blocks bz #1028285 because the latter adds VDSO support for gettimeofday, which in turn introduces this bug.

Comment 18 errata-xmlrpc 2014-10-14 04:43:44 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2014-1391.html


Note You need to log in before you can comment on or make changes to this bug.