[Bug 292496] linux_timer_create error when using LINUX_CLOCK_MONOTONIC
[email protected] Fri, 16 Jan 2026 13:42:54 +0000
| Newsgroups | gmane.os.freebsd.devel.emulation |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292496 Warner Losh <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open CC| |[email protected] --- Comment #1 from Warner Losh <[email protected]> --- > After the commit, linux_to_native_clockid started returning CLOCK_UPTIME. Next, CLOCK_UPTIME is passed to kern_ktimer_create (sys/kern/kern_time.c), which returns EINVAL when checking if (clock_id < 0 || clock_id >= MAX_CLOCKS), since MAX_CLOCKS = 5 and CLOCK_UPTIME is also equal to 5. But #define MAX_CLOCKS (CLOCK_TAI+1) and #define CLOCK_TAI 16 In both current and stable. How can MAX_CLOCKS be 5? Examining the code suggests it should be fine. Can you dig in a little deeper in your environment to see what's going on? -- You are receiving this mail because: You are the assignee for the bug.