<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hello Andrew,<br>
      <br>
      <style type="text/css"><!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}--></style><span
        style="font-size: 13px;"
        data-sheets-value="{"1":2,"2":"&
        core.StackAddressEscape Check that addresses to stack memory do
        not escape the function"}"
data-sheets-userformat="{"2":515,"3":[null,0],"4":[null,2,16776960],"12":0}">core.StackAddressEscape
        - I think this checker should work for kernel well.<br>
      </span>core.builtin.NoReturnFunctions - this service checker
      should decrease the amount of FPs reported due to analyzing of
      unreachable paths. It may need some tuning for kernel (adding
      kernel no-return functions). I vote for enabling it.<br>
      For unix.Malloc checker we should add the support for kernel
      memory  allocation functions like kmalloc/kfree. The same for
      PthreadLock and CString*. When it's done, they may be also
      enabled.<br>
      <style type="text/css"><!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}--></style><span
        style="font-size:13px;font-family:arial,sans,sans-serif;"
        data-sheets-value="{"1":2,"2":"alpha.security.taint.TaintPropagation
        Generate taint information used by other checkers"}"
data-sheets-userformat="{"2":513,"3":[null,0],"12":0}">alpha.security.taint.TaintPropagation
        may help other checkers to find taint-related issues. I think it
        should be enabled.<br>
        <br>
      </span><br>
      <meta name="generator" content="Sheets">
      <style type="text/css"><!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}--></style><br>
      25.05.2016 21:47, Andrew Wells via cfe-dev пишет:<br>
    </div>
    <blockquote
cite="mid:CAN_h2FWYbOtiLvzCe6H5ES8hCGh0Vb-8hckdPoFsB2xxMLte0Q@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hi, I'm a student in GSoC working on the LLVMLinux
        project trying to get the Clang static analyzer working with the
        kernel.  I'm in the process of sorting through which checkers
        are or are not applicable to the kernel.   I was wondering if
        anyone could give me a run-down on the state of the alpha
        checkers, ie. what issues they have for this project.  Also I
        have a list of checkers color-coded by which ones are applicable
        to the kernel.  If you have some free-time and want to save me
        some headache would you mind pointing out any obvious mistakes
        with the list. <a moz-do-not-send="true"
href="https://docs.google.com/spreadsheets/d/1wt1hNl1tqY8XjSZmZCydfa2yZqKXDSvDT0uVxDutRHA/edit#gid=0">https://docs.google.com/spreadsheets/d/1wt1hNl1tqY8XjSZmZCydfa2yZqKXDSvDT0uVxDutRHA/edit#gid=0</a>
        <div><br>
        </div>
        <div>Thanks for the help.</div>
        <div><br>
        </div>
        <div>--Andrew Wells</div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
cfe-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>
<a class="moz-txt-link-freetext" href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>