<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in futex_wait_timeout.c</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>fbf4dec7 - selftests/futex: Order calls to futex_lock_pi</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c#fbf4dec7</link>
        <description>selftests/futex: Order calls to futex_lock_piObserved occassional failures in the futex_wait_timeout test:ok 1 futex_wait relative succeedsok 2 futex_wait_bitset realtime succeedsok 3 futex_wait_bitset monotonic succeedsok 4 futex_wait_requeue_pi realtime succeedsok 5 futex_wait_requeue_pi monotonic succeedsnot ok 6 futex_lock_pi realtime returned 0......The test expects the child thread to complete some steps beforethe parent thread gets to run. There is an implicit expectationof the order of invocation of futex_lock_pi between the child threadand the parent thread. Make this order explicit. If the order isnot met, the futex_lock_pi call in the parent thread succeeds andwill not timeout.Fixes: f4addd54b161 (&quot;selftests: futex: Expand timeout test&quot;)Signed-off-by: Nysal Jan K.A &lt;nysal@linux.ibm.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c</description>
        <pubDate>Mon, 14 Aug 2023 08:09:27 +0000</pubDate>
        <dc:creator>Nysal Jan K.A &lt;nysal@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>02e56ccb - selftests: futex: Test sys_futex_waitv() timeout</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c#02e56ccb</link>
        <description>selftests: futex: Test sys_futex_waitv() timeoutTest if the futex_waitv timeout is working as expected, using thesupported clockid options.Signed-off-by: Andr&#233; Almeida &lt;andrealmeid@collabora.com&gt;Signed-off-by: Peter Zijlstra (Intel) &lt;peterz@infradead.org&gt;Link: https://lore.kernel.org/r/20210923171111.300673-21-andrealmeid@collabora.com

            List of files:
            /linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c</description>
        <pubDate>Thu, 23 Sep 2021 17:11:09 +0000</pubDate>
        <dc:creator>Andr&#233; Almeida &lt;andrealmeid@collabora.com&gt;</dc:creator>
    </item>
<item>
        <title>f4addd54 - selftests: futex: Expand timeout test</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c#f4addd54</link>
        <description>selftests: futex: Expand timeout testImprove futex timeout testing by checking all the operations thatsupports timeout and their available modes.Signed-off-by: Andr&#233; Almeida &lt;andrealmeid@collabora.com&gt;Signed-off-by: Ingo Molnar &lt;mingo@kernel.org&gt;Link: https://lore.kernel.org/r/20210427135328.11013-3-andrealmeid@collabora.com

            List of files:
            /linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c</description>
        <pubDate>Tue, 27 Apr 2021 13:53:28 +0000</pubDate>
        <dc:creator>Andr&#233; Almeida &lt;andrealmeid@collabora.com&gt;</dc:creator>
    </item>
<item>
        <title>2874c5fd - treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 152</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c#2874c5fd</link>
        <description>treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 152Based on 1 normalized pattern(s):  this program is free software you can redistribute it and or modify  it under the terms of the gnu general public license as published by  the free software foundation either version 2 of the license or at  your option any later versionextracted by the scancode license scanner the SPDX license identifier  GPL-2.0-or-laterhas been chosen to replace the boilerplate/reference in 3029 file(s).Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Reviewed-by: Allison Randal &lt;allison@lohutok.net&gt;Cc: linux-spdx@vger.kernel.orgLink: https://lkml.kernel.org/r/20190527070032.746973796@linutronix.deSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c</description>
        <pubDate>Mon, 27 May 2019 06:55:01 +0000</pubDate>
        <dc:creator>Thomas Gleixner &lt;tglx@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>5821ba96 - selftests: Add test plan API to kselftest.h and adjust callers</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c#5821ba96</link>
        <description>selftests: Add test plan API to kselftest.h and adjust callersThe test plan for TAP needs to be declared immediately after the header.This adds the test plan API to kselftest.h and updates all callers todeclare their expected test counts.Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c</description>
        <pubDate>Wed, 24 Apr 2019 23:12:37 +0000</pubDate>
        <dc:creator>Kees Cook &lt;keescook@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>b274e75c - selftests: futex: convert test to use ksft TAP13 framework</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c#b274e75c</link>
        <description>selftests: futex: convert test to use ksft TAP13 frameworkConvert test to use ksft TAP13 framework to print user friendlytest output which is consistent across kselftest suite.Acked-by: Darren Hart (VMware) &lt;dvhart@infradead.org&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c</description>
        <pubDate>Fri, 04 Aug 2017 23:12:29 +0000</pubDate>
        <dc:creator>Shuah Khan &lt;shuahkh@osg.samsung.com&gt;</dc:creator>
    </item>
<item>
        <title>1f666e52 - selftests: futex: print testcase-name and PASS/FAIL/ERROR status</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c#1f666e52</link>
        <description>selftests: futex: print testcase-name and PASS/FAIL/ERROR statusMost of the tests under selftests follow a pattern for their results,which can then be parsed easily by other external tools easily. Thoughfutex tests do print the test results very well, it doesn&apos;t reallyfollow the general selftests pattern.This patch makes necessary changes to fix that.Output before this patch:futex_requeue_pi: Test requeue functionality        Arguments: broadcast=0 locked=0 owner=0 timeout=0nsResult:  PASSOutput after this patch:futex_requeue_pi: Test requeue functionality        Arguments: broadcast=0 locked=0 owner=0 timeout=0nsselftests: futex-requeue-pi [PASS]Signed-off-by: Naresh Kamboju &lt;naresh.kamboju@linaro.org&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c</description>
        <pubDate>Mon, 22 May 2017 07:17:43 +0000</pubDate>
        <dc:creator>Naresh Kamboju &lt;naresh.kamboju@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>2aa8470f - selftests: Add futex functional tests</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c#2aa8470f</link>
        <description>selftests: Add futex functional testsThe futextest testsuite [1] provides functional, stress, andperformance tests for the various futex op codes. Those tests will be ofmore use to futex developers if they are included with the kernelsource.Copy the core infrastructure and the functional tests into selftests,but adapt them for inclusion in the kernel:- Update the Makefile to include the run_tests target, remove reference  to the performance and stress tests from the contributed sources.- Replace my dead IBM email address with my current Intel email address.- Remove the warrantee and write-to paragraphs from the license blurbs.- Remove the NAME section as the filename is easily determined. ;-)- Make the whitespace usage consistent in a couple of places.- Cleanup various CodingStyle violations.A future effort will explore moving the performance and stress testsinto the kernel.1. http://git.kernel.org/cgit/linux/kernel/git/dvhart/futextest.gitCc: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;Cc: linux-api@vger.kernel.orgCc: Ingo Molnar &lt;mingo@elte.hu&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;Cc: Davidlohr Bueso &lt;dave@stgolabs.net&gt;Cc: KOSAKI Motohiro &lt;kosaki.motohiro@jp.fujitsu.com&gt;Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/futex/functional/futex_wait_timeout.c</description>
        <pubDate>Wed, 13 May 2015 04:07:52 +0000</pubDate>
        <dc:creator>Darren Hart &lt;dvhart@linux.intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
