Re: kern/59127 (clock_getres(2) returns EINVAL for CLOCK_{PROCESS,THREAD}_CPUTIME_ID)

To: gnats-bugs%netbsd.org@localhost, kern-bug-people%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, riastradh%NetBSD.org@localhost
Subject: Re: kern/59127 (clock_getres(2) returns EINVAL for CLOCK_{PROCESS,THREAD}_CPUTIME_ID)
From: PHO <pho%cielonegro.org@localhost>
Date: Thu, 27 Mar 2025 17:09:44 +0900

Does this need pullup-9, pullup-10?

I don't think so, because it was just a missing feature and wasn'treally a bug.

The test case still has an atf_tc_expect_fail.  Why is that?  If the
bug is fixed, there should be no atf_tc_expect_fail left.  If the bug
is still there, there should be an open PR for it, cited in the
atf_tc_expect_fail message.

Because I don't know what to do. Our clock_settime.2 lists twoadditional clocks CLOCK_VIRTUAL and CLOCK_PROF which neitherclock_gettime(2) nor clock_getres(2) support. These syscalls both returnEINVAL for these clocks. Do you have any idea why they are listed at all?

References:
- Re: kern/59127 (clock_getres(2) returns EINVAL for CLOCK_{PROCESS,THREAD}_CPUTIME_ID)
  - From: riastradh

Prev by Date: Re: kern/59127 (clock_getres(2) returns EINVAL for CLOCK_{PROCESS,THREAD}_CPUTIME_ID)
Next by Date: misc/59226: Build failure on Solaris-11.4 in src/share/mk/bsd.test.mk
Previous by Thread: Re: kern/59127 (clock_getres(2) returns EINVAL for CLOCK_{PROCESS,THREAD}_CPUTIME_ID)
Next by Thread: Re: kern/59127 (clock_getres(2) returns EINVAL for CLOCK_{PROCESS,THREAD}_CPUTIME_ID)
Indexes:

Home | Main Index | Thread Index | Old Index