Repository navigation
fix(libkernel): reject unsupported condition clocks - #2116
Closed
STUPIDCONTEM wants to merge 1 commit into
Closed
STUPIDCONTEM wants to merge 1 commit into
STUPIDCONTEM wants to merge 1 commit into
Conversation
Collaborator
|
Closing for the same reason as #2089: an unsupported clock already fails explicitly on main when a timed wait uses it, and no title is shown passing one. Reopen with the title ID and the log line if you find one. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Evidence review (2026-10-09)
Closed by maintainer; not ready to reopen. Required evidence: Title ID and a log showing a title supplies an unsupported condition clock; existing failure at wait is deliberate.
Game/title ID: none verified. No PS5 title execution is claimed.
What
Validate
pthread_condattr_setclockbefore storing a clock ID. FreeBSD condition attributes accept IDs 0, 1, 2 and 4 (REALTIME, VIRTUAL, PROF and MONOTONIC); other values now return guest EINVAL without changing the attribute or guest errno. Previously every ID was stored, so a later timed wait could reach an unsupported clock path.The accepted set comes directly from FreeBSD stable/11
_pthread_condattr_setclock. This is narrower than the set of clocks valid for clock_gettime: ID 5 is valid globally but unsupported for this attribute. The POSIX setter correction is distinct from #2089's clock-query errors and #2111's deadline arithmetic.Tested
Windows 10 Pro 19045, WinLibs GCC 15.2 UCRT posix SEH r7, Release, BUILD_TESTING=ON, main 6cc0503.
No Linux or title execution is claimed for this new correction.
Checklist