<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/git/next/linux-next.git/lib/test_csd_lock.c, branch master</title>
<subtitle>The linux-next integration testing tree</subtitle>
<id>https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/atom?h=master</id>
<link rel='self' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/'/>
<updated>2026-08-24T00:01:46+00:00</updated>
<entry>
<title>lib/test_csd_lock: Add a module to stall a CPU on a CSD lock</title>
<updated>2026-08-24T00:01:46+00:00</updated>
<author>
<name>Breno Leitao</name>
<email>leitao@debian.org</email>
</author>
<published>2026-08-10T11:29:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=915312ce14447560e21258be05d44fb7d6e84a4f'/>
<id>urn:sha1:915312ce14447560e21258be05d44fb7d6e84a4f</id>
<content type='text'>
Add test_csd_lock, a module that keeps one CPU from answering an IPI for
as long as its stall_ms parameter says, so that the CSD-lock debug code
has a stall to report.  With in_handler=1 the CPU stalls inside a CSD
handler instead, which is the case where the IPI is not re-sent.

The module needs CONFIG_CSD_LOCK_WAIT_DEBUG and csdlock_debug=1.  Loading
it runs one stall and then fails the load with -EAGAIN, the way
test_lockup does, so that nothing is left loaded afterwards.

Signed-off-by: Breno Leitao &lt;leitao@debian.org&gt;
Signed-off-by: Paul E. McKenney &lt;paulmck@kernel.org&gt;
</content>
</entry>
</feed>
