Hi,
On 03/17/2015 08:53 PM, Cyril Hrubis wrote:
> Hi!
>> Signed-off-by: Xiaoguang Wang <wangxg.f...@cn.fujitsu.com>
>> ---
>> testcases/kernel/syscalls/futex/futex_wait_bitset.h | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/testcases/kernel/syscalls/futex/futex_wait_bitset.h
>> b/testcases/kernel/syscalls/futex/futex_wait_bitset.h
>> index 2f8ddb8..73d87da 100644
>> --- a/testcases/kernel/syscalls/futex/futex_wait_bitset.h
>> +++ b/testcases/kernel/syscalls/futex/futex_wait_bitset.h
>> @@ -42,6 +42,12 @@ static void verify_futex_wait_bitset(long long wait_us,
>> clock_t clk_id)
>> return;
>> }
>>
>> + if (TEST_ERRNO == EOPNOTSUPP || TEST_ERRNO == ENOSYS) {
>> + tst_resm(TCONF, "In this kernel, futex() does not support "
>> + "FUTEX_WAIT_BITSET operation");
>> + return;
>> + }
>
> On which system did you get EOPNOTSUPP? The (incomplete) futex man page
> only defines ENOSYS if futex op is not defined. Or was that only for
> FUTEX_CLOCK_REALTIME?
This ENOSYS is for EOPNOTSUPP operation. Actually I only get ENOSYS in
RHEL5.11GA, so will remove the EOPNOTSUPP check.
>
> A bit more background info in the commit message would not harm,
> otherwise the patch looks OK.
OK, thanks!
Regards,
Xiaoguang Wang
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
