From: Norbert Manthey <nmanthey@amazon.de>
To: dan.carpenter@oracle.com
Cc: smatch@vger.kernel.org,
"Julian Stecklina (jsteckli)" <jsteckli@amazon.de>
Subject: smatch validation tests fail
Date: Fri, 3 Aug 2018 16:03:47 +0200 [thread overview]
Message-ID: <14c0dce0-1184-79f5-22e1-ce54b35ff4ce@amazon.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
Dear Dan,
I started to look into porting smatch to be applicable to other code
bases and projects. When trying to get taint analysis working for Xen, I
also gave the validation tests of smatch a try and noticed that
user_data test 3 fails. I attached the relevant part of the log of my
call. Is that failure a known problem that I should ignore, or might
this bug explain why taint analysis for Xen is not working as it's
working for Linux (essentially, I added copy_from_guest where smatch
uses copy_from_user). This is what I executed:
git rev-parse --short HEAD
b787aa7
make check &> check.log; echo $?
2
Furthermore, I wonder whether smatch is sensitive to the current working
directory. While for Linux, gcc seems to be called from the repository
root each time, in Xen gcc is called next to the current source file. In
case I run smatch in addition to each Xen gcc call, the current working
directory will be different as well. Is that a problem for smatch, or
can I expect it to behave as for the kernel? Unfortunately, I did not
find anything about this behavior in the docs.
Thanks for any help!
Best,
Norbert
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
[-- Attachment #2: check.log.gz --]
[-- Type: application/gzip, Size: 788 bytes --]
next reply other threads:[~2018-08-03 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 14:03 Norbert Manthey [this message]
2018-08-06 9:53 ` smatch validation tests fail Dan Carpenter
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=14c0dce0-1184-79f5-22e1-ce54b35ff4ce@amazon.de \
--to=nmanthey@amazon.de \
--cc=dan.carpenter@oracle.com \
--cc=jsteckli@amazon.de \
--cc=smatch@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).