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 17:05:16 +0200 [thread overview]
Message-ID: <59fac17e-7272-2098-15f5-d89473d75e13@amazon.de> (raw)
In-Reply-To: <20180814145220.uzmcdwh3guqeb2kh@mwanda>
Alright, the patches are out. The list is not complete, but it's a start
that should allow to get the first taint information for Xen as well. I
hope they make sense. Given my limited experience with smatch, I might
have made mistakes.
I spotted limits during compilation, and increased a few. I guess there
are more. I'll play with it and might increase some others eventually,
to get more coverage.
Best,
Norbert
On 08/14/2018 04:52 PM, Dan Carpenter wrote:
> On Tue, Aug 14, 2018 at 04:33:15PM +0200, Norbert Manthey wrote:
>> Oh, that's nice. I'll play with the new script.
>>
>> Concerning the copy from user functions, I have a few patches locally to
>> get the functions into the tool, which I just have to make a little
>> nicer before sharing. I will post them once done.
>
> Forget about making it nice. Just send it. :)
>
>> I found the
>> "copy_from_guest" string also at other places, as well as matching
>> syscalls which come with a user controllable argument. The patches
>> should cover all those.
>
> In the kernel, syscalls should be covered. Historically, it does matter
> how the kernel is configured, but hopefully we've fixed those bugs.
> Also we keep changing the SYS_CALL macros, so I can't swear that all
> versions work.
>
> regars,
> 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 17:53 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
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 [this message]
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=59fac17e-7272-2098-15f5-d89473d75e13@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;
as well as URLs for NNTP newsgroup(s).