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 1064945 - ftime() possibly broken on ppc
Summary: ftime() possibly broken on ppc
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glibc
Version: 7.0
Hardware: ppc
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: Siddhesh Poyarekar
QA Contact: Arjun Shankar
URL:
Whiteboard:
Depends On:
Blocks: 1099025
TreeView+ depends on / blocked
 
Reported: 2014-02-13 15:32 UTC by Miroslav Lichvar
Modified: 2016-11-24 12:12 UTC (History)
6 users (show)

Fixed In Version: glibc-2.17-49.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1099025 (view as bug list)
Environment:
Last Closed: 2014-06-13 12:56:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Miroslav Lichvar 2014-02-13 15:32:56 UTC
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 4 Siddhesh Poyarekar 2014-02-21 10:49:05 UTC
This is upstream 16430:

https://sourceware.org/bugzilla/show_bug.cgi?id=16430

Checking for backport feasibility.

Comment 6 Siddhesh Poyarekar 2014-02-24 04:23:58 UTC
A straight backport of https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=736c304a1ab4cee36a2f3343f1698bc0abae4608 fixes the problem.  No regressions seen in the testsuite.  Carlos, could you mark devel_ack+ so that I can push it?

Comment 11 Ludek Smid 2014-06-13 12:56:40 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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