Re: [LTP] [PATCH] openposix: update invalid clock id to accomodate new auxiliary clock ids

[Cyril Hrubis <chrubis@suse.cz>]

Hi!
> There can be 8 more clock ids reserved on systems with
> CONFIG_POSIX_AUX_CLOCK=y [1]
> consequently clock 17 no longer remains an invalid id.
> 
> [1] https://lkml.org/lkml/2025/5/19/341
> 
> Signed-off-by: Avinesh Kumar <akumar@suse.de>
> ---
>  .../conformance/interfaces/clock_getres/6-2.c                 | 4 ++--
>  .../conformance/interfaces/clock_gettime/8-2.c                | 4 ++--
>  .../conformance/interfaces/clock_settime/17-2.c               | 4 ++--
>  3 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/testcases/open_posix_testsuite/conformance/interfaces/clock_getres/6-2.c b/testcases/open_posix_testsuite/conformance/interfaces/clock_getres/6-2.c
> index c44809012..62de33c4f 100644
> --- a/testcases/open_posix_testsuite/conformance/interfaces/clock_getres/6-2.c
> +++ b/testcases/open_posix_testsuite/conformance/interfaces/clock_getres/6-2.c
> @@ -17,7 +17,7 @@
>   *   unassigned value = -1073743192 (ex. of what gcc will set to)
>   *   unassigned value = 1073743192 (ex. of what gcc will set to)
>   *   -1
> - *   17 (currently not = to any clock)
> + *   25 (not associated to any clock, considering posix auxiliary clocks also)

Technically you can have any number of clocks defined by a system that
implements POSIX. So the comment here should be:

"hopefully big enough not to be a valid clock value"

And we may possibly bump it to a larger value as well, e.g. 50


-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp