From: Norbert Manthey <nmanthey@amazon.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Norbert Manthey <norbertmanthey@googlemail.com>,
smatch@vger.kernel.org, jsteckli@amazon.com,
tautschn@amazon.co.uk
Subject: Re: Smatch for Xen
Date: Tue, 14 Aug 2018 15:27:43 +0200 [thread overview]
Message-ID: <bbe9f3aa-1ec8-5004-1d4e-c29eb6868058@amazon.de> (raw)
In-Reply-To: <20180813183132.suxab5gfub5uig2k@mwanda>
Thanks a lot! I used your scripts and compiled Xen now, as well as
created the data base for it. As I am interested in analysis that is run
for the kernel, I also asked the tool to name the project "kernel", as
that enabled this analysis (e.g. the spectre analysis).
I called the build_xen_data.sh scripts multiple times on an upstream Xen
release branch, and the number of warnings did not increase, while for
the Linux kernel the number of warnings would increase, e.g. warnings
that depend on the taint analysis like the spectre analysis. Is that
expected, and is there a way to improve that for Xen?
Best,
Norbert
On 08/13/2018 08:31 PM, Dan Carpenter wrote:
> Ahh... Never mind. My mistake. It should have just been:
>
> cat SMATCH/smatch/results/*.c > smatch_warns.txt
>
> The next problem is that I don't seem to be pulling in the
> include/xen/compiler.h header file...
>
> regards,
> dan carpenter
>
>
Amazon Development Center Germany GmbH
Berlin - Dresden - Aachen
main office: Krausenstr. 38, 10117 Berlin
Geschaeftsfuehrer: Dr. Ralf Herbrich, Christian Schlaeger
Ust-ID: DE289237879
Eingetragen am Amtsgericht Charlottenburg HRB 149173 B
next prev parent reply other threads:[~2018-08-14 16:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 12:40 Smatch for Xen Norbert Manthey
2018-07-30 16:34 ` [PATCH 0/3] add support for mode __pointer__ & __byte__ Luc Van Oostenryck
2018-07-30 16:34 ` [PATCH 1/3] mode keywords don't need MOD_{CHAR,LONG,...} Luc Van Oostenryck
2018-07-30 16:34 ` [PATCH 2/3] add support for mode __pointer__ Luc Van Oostenryck
2018-07-30 16:34 ` [PATCH 3/3] add support for mode __byte__ Luc Van Oostenryck
2018-08-06 10:31 ` Smatch for Xen Dan Carpenter
2018-08-06 11:20 ` Dan Carpenter
2018-08-06 13:16 ` Dan Carpenter
[not found] ` <CAByO1we3OABkX8XCwh7Vq8iHyXAuFtJ3t+Ta3DVCLe9pP6K8ew@mail.gmail.com>
2018-08-06 13:54 ` Dan Carpenter
2018-08-13 14:25 ` Norbert Manthey
2018-08-13 17:58 ` Dan Carpenter
2018-08-13 18:31 ` Dan Carpenter
2018-08-14 13:27 ` Norbert Manthey [this message]
2018-08-14 14:21 ` Dan Carpenter
2018-08-14 14:33 ` Norbert Manthey
2018-08-14 14:52 ` Dan Carpenter
2018-08-14 15:05 ` Norbert Manthey
2018-08-15 9:03 ` Dan Carpenter
2018-08-15 13:44 ` Norbert Manthey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bbe9f3aa-1ec8-5004-1d4e-c29eb6868058@amazon.de \
--to=nmanthey@amazon.de \
--cc=dan.carpenter@oracle.com \
--cc=jsteckli@amazon.com \
--cc=norbertmanthey@googlemail.com \
--cc=smatch@vger.kernel.org \
--cc=tautschn@amazon.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox