<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - vtn_vector_construct writing out of bounds when given multiple non-zero length sources"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99465">99465</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>vtn_vector_construct writing out of bounds when given multiple non-zero length sources
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>13.0
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Other
</td>
</tr>
<tr>
<th>Assignee</th>
<td>mesa-dev@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>freiling@google.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>mesa-dev@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>We ran into this problem running the correctness test for the skia graphics
library on Vulkan on Linux on Intel HD520, it was causing a number of memory
corruption issues and segfaults in different tests. You can reproduce the
problem by running the Skia correctness tests
(<a href="https://skia.org/dev/testing/testing">https://skia.org/dev/testing/testing</a>) on their vulkan backend
(<a href="https://skia.org/user/special/vulkan">https://skia.org/user/special/vulkan</a>). This may be the cause of
<a class="bz_bug_link
bz_status_NEW "
title="NEW - SIGSEGV - spirv_to_nir - in vkQuake"
href="show_bug.cgi?id=97213">https://bugs.freedesktop.org/show_bug.cgi?id=97213</a>
The solution we used (<a href="https://fuchsia-review.googlesource.com/c/17700/">https://fuchsia-review.googlesource.com/c/17700/</a>) was to
make the total number of components in the output vector the sum of all the
components in all of the input vectors. This fixes the memory corruption, but
it remains unclear to us if this is the correct behavior for the compiler,
which is why we havent submitted an upstream patch yet.
Let me know if you need anything else from my end on this.
Cheers,
Forrest Reiling</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>