<html>
<head>
<base href="https://bugs.llvm.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 - Handling SIOCETHTOOL ioctls would be useful"
href="https://bugs.llvm.org/show_bug.cgi?id=45814">45814</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Handling SIOCETHTOOL ioctls would be useful
</td>
</tr>
<tr>
<th>Product</th>
<td>compiler-rt
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>msan
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>gharris@sonic.net
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>In compiler-rt/lib/sanitizer_common there appear to be "interceptors" for
various ioctl calls, to indicate what fetches and stores are done by the ioctls
in question.
There does not appear to be a handler for SIOCETHTOOL. This caused the memory
sanitizer to report that code similar to the example in
<a href="https://www.linuxjournal.com/article/6908">https://www.linuxjournal.com/article/6908</a> of how to use the ETHTOOL_GLINK
command for SIOCETHTOOL to report a reference to uninitialized memory when it
tested the .data member of the structure pointed to by the ifr_data member of
the fires structure in that call.
This would be a bit of a pain to fix, as the behavior of SIOCETHTOOL depends on
the particular command passed to it, so you can't use the table filled in by
ioctl_table_fill() - SIOCETHTOOL would have to be handled by special code,
which could itself be table-driven.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>