<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/kernel/kcsan/kcsan-test.c, branch linux-5.10.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.10.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.10.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2023-02-01T07:23:16Z</updated>
<entry>
<title>kcsan: test: don't put the expect array on the stack</title>
<updated>2023-02-01T07:23:16Z</updated>
<author>
<name>Max Filippov</name>
</author>
<published>2022-12-23T07:28:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3b154d5204ff8aa82a2bd4d5ed29a7cf80723706'/>
<id>urn:sha1:3b154d5204ff8aa82a2bd4d5ed29a7cf80723706</id>
<content type='text'>
[ Upstream commit 5b24ac2dfd3eb3e36f794af3aa7f2828b19035bd ]

Size of the 'expect' array in the __report_matches is 1536 bytes, which
is exactly the default frame size warning limit of the xtensa
architecture.
As a result allmodconfig xtensa kernel builds with the gcc that does not
support the compiler plugins (which otherwise would push the said
warning limit to 2K) fail with the following message:

  kernel/kcsan/kcsan_test.c:257:1: error: the frame size of 1680 bytes
    is larger than 1536 bytes

Fix it by dynamically allocating the 'expect' array.

Signed-off-by: Max Filippov &lt;jcmvbkbc@gmail.com&gt;
Reviewed-by: Marco Elver &lt;elver@google.com&gt;
Tested-by: Marco Elver &lt;elver@google.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>kcsan: Test support for compound instrumentation</title>
<updated>2020-08-24T22:09:58Z</updated>
<author>
<name>Marco Elver</name>
</author>
<published>2020-07-24T07:00:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bec4a2474890a6884eb890c778ea02bccaaae6eb'/>
<id>urn:sha1:bec4a2474890a6884eb890c778ea02bccaaae6eb</id>
<content type='text'>
Changes kcsan-test module to support checking reports that include
compound instrumentation. Since we should not fail the test if this
support is unavailable, we have to add a config variable that the test
can use to decide what to check for.

Acked-by: Peter Zijlstra (Intel) &lt;peterz@infradead.org&gt;
Signed-off-by: Marco Elver &lt;elver@google.com&gt;
Signed-off-by: Paul E. McKenney &lt;paulmck@kernel.org&gt;
</content>
</entry>
<entry>
<title>kcsan: Add atomic builtin test case</title>
<updated>2020-08-24T22:09:31Z</updated>
<author>
<name>Marco Elver</name>
</author>
<published>2020-07-03T13:40:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f9ea63193135473ed6b6ff06f016eb6248100041'/>
<id>urn:sha1:f9ea63193135473ed6b6ff06f016eb6248100041</id>
<content type='text'>
Adds test case to kcsan-test module, to test atomic builtin
instrumentation works.

Signed-off-by: Marco Elver &lt;elver@google.com&gt;
Signed-off-by: Paul E. McKenney &lt;paulmck@kernel.org&gt;
</content>
</entry>
<entry>
<title>kcsan: Add jiffies test to test suite</title>
<updated>2020-06-29T19:04:48Z</updated>
<author>
<name>Marco Elver</name>
</author>
<published>2020-06-16T12:36:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=56b031f0abf55254d47a329010574733fa9a27b8'/>
<id>urn:sha1:56b031f0abf55254d47a329010574733fa9a27b8</id>
<content type='text'>
Add a test that KCSAN nor the compiler gets confused about accesses to
jiffies on different architectures.

Signed-off-by: Marco Elver &lt;elver@google.com&gt;
Signed-off-by: Paul E. McKenney &lt;paulmck@kernel.org&gt;
</content>
</entry>
<entry>
<title>kcsan: Prefer '__no_kcsan inline' in test</title>
<updated>2020-06-29T19:04:48Z</updated>
<author>
<name>Marco Elver</name>
</author>
<published>2020-06-02T14:36:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2888557f68db334a3839dcc262264a4c436f576b'/>
<id>urn:sha1:2888557f68db334a3839dcc262264a4c436f576b</id>
<content type='text'>
Instead of __no_kcsan_or_inline, prefer '__no_kcsan inline' in test --
this is in case we decide to remove __no_kcsan_or_inline.

Suggested-by: Peter Zijlstra &lt;peterz@infradead.org&gt;
Signed-off-by: Marco Elver &lt;elver@google.com&gt;
Signed-off-by: Paul E. McKenney &lt;paulmck@kernel.org&gt;
</content>
</entry>
<entry>
<title>kcsan: Add test suite</title>
<updated>2020-06-29T19:04:48Z</updated>
<author>
<name>Marco Elver</name>
</author>
<published>2020-05-05T18:28:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1fe84fd4a4027a17d511a832f89ab14107650ba4'/>
<id>urn:sha1:1fe84fd4a4027a17d511a832f89ab14107650ba4</id>
<content type='text'>
This adds KCSAN test focusing on behaviour of the integrated runtime.
Tests various race scenarios, and verifies the reports generated to
console. Makes use of KUnit for test organization, and the Torture
framework for test thread control.

Signed-off-by: Marco Elver &lt;elver@google.com&gt;
Signed-off-by: Paul E. McKenney &lt;paulmck@kernel.org&gt;
</content>
</entry>
</feed>
