[llvm-bugs] [Bug 45814] New: Handling SIOCETHTOOL ioctls would be useful

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=45814

            Bug ID: 45814
           Summary: Handling SIOCETHTOOL ioctls would be useful
           Product: compiler-rt
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: msan
          Assignee: unassignedbugs at nondot.org
          Reporter: gharris at sonic.net
                CC: llvm-bugs at lists.llvm.org

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
https://www.linuxjournal.com/article/6908 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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200506/727f06ef/attachment-0001.html>