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

[Avinesh Kumar <akumar@suse.de>]

Hi Cyril,

On Monday, October 6, 2025 11:08:35 AM CEST you wrote:
> 
> Hi!
> > 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
> 
> Or we may be a bit smarter, for clock_gettime() or clock_getres() we can
> loop starting at 0 until we get EINVAL or cross sufficiently large value.
> 
> 
I thought of implementing something like this. But we get EINVAL for
smaller values also for which clocks are not defined.

./clock_getres_6-2.run-test 
clock_getres(-2147483648, &res);
clock_getres(2147483647, &res);
clock_getres(2147483647, &res);
clock_getres(-2147483647, &res);
clock_getres(-1073743192, &res);
clock_getres(1073743192, &res);
clock_getres(-1, &res);
clock_getres(10, &res);
clock_getres(11, &res);
clock_getres() != -1
clock_getres(12, &res);
clock_getres(13, &res);
clock_getres(14, &res);
clock_getres(15, &res);
clock_getres(16, &res);
clock_getres() != -1
clock_getres(17, &res);
clock_getres() != -1
clock_getres(18, &res);
clock_getres() != -1
clock_getres(19, &res);
clock_getres() != -1
clock_getres(20, &res);
clock_getres() != -1
clock_getres(21, &res);
clock_getres() != -1
clock_getres(22, &res);
clock_getres() != -1
clock_getres(23, &res);
clock_getres() != -1
clock_getres(24, &res);
clock_getres(25, &res);
clock_getres(26, &res);
At least one test FAILED -- see above




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