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.

Created attachment 431431 [details]
testprogram

Description of problem:
Strace doesn't show when you call clock_gettime. If we compare this with our 5.4 machine where it shows.

Version-Release number of selected component (if applicable):
strace-4.5.19-1.5.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Program:
$ cat testclock.c
#include <time.h>
#include <stdio.h>

int main(void)
{
  int intRet;
  struct timespec res;

  intRet = clock_gettime(CLOCK_REALTIME, &res);
}

2. gcc -o testclock -lrt testclock.c

3. strace ./testclock


Actual results:
A strace without any information about calling clock_gettime


Expected results:
Strace should get a result similair to the below (taken from a Red Hat Enterprise 5.4 environment):
clock_gettime(CLOCK_REALTIME, {1279021215, 132738000}) = 0


Additional info:
See attachment for the whole strace results.

Created attachment 431432 [details]
strace of testclock on a 5.4

Created attachment 431433 [details]
strace of testclock on 6.0 Beta

There is no bug here.  The clock_gettime call on x86_64 can now sometimes work via the kernel-supplied vDSO without making a syscall.  strace can't trace the call into the vDSO, since it's just user-mode code (albeit kernel-supplied).