From: Dan Carpenter <dan.carpenter@oracle.com>
To: Andrew Murray <andrew.murray@arm.com>
Cc: smatch@vger.kernel.org
Subject: Re: Detecting user data on base types
Date: Thu, 6 Jun 2019 13:15:09 +0300 [thread overview]
Message-ID: <20190606101509.GY24680@kadam> (raw)
In-Reply-To: <20190605122841.GD23647@e119886-lin.cambridge.arm.com>
On Wed, Jun 05, 2019 at 01:28:41PM +0100, Andrew Murray wrote:
> Actually it looks there is logic associated to get_user in handle_get_user within
> smatch_kernel_user_data.c - however this doesn't seem to trigger in the following (it looks
> like it does something with the return value of the macro, but this is just an error flag):
>
> do_pages_move -calls-> add_page_for_migration - the second argument of
> add_page_for_migration 'addr' comes from get_user - but it isn't marked as USER_DATA in
> the database. I don't understand why this is.
>
That's weird. It's working for me.
mm/migrate.c | do_pages_move | add_page_for_migration | USER_DATA | 1 | addr | 0-u64max
Btw, I pushed the fix for untagged_addr() and my DB was built with that
fix. You could try see if that makes a difference, I guess?
kchecker --info mm/migrate.c > info.txt
~/path/to/smatch/smatch_data/db/reload_partial.sh info.txt
regards,
dan carpenter
next prev parent reply other threads:[~2019-06-06 10:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 18:47 Detecting user data on base types Andrew Murray
2019-05-29 19:49 ` Dan Carpenter
2019-05-30 9:03 ` Andrew Murray
2019-05-30 17:46 ` Dan Carpenter
2019-06-05 8:29 ` Andrew Murray
2019-06-05 11:47 ` Andrew Murray
2019-06-05 12:28 ` Andrew Murray
2019-06-06 10:15 ` Dan Carpenter [this message]
2019-06-13 10:41 ` Andrew Murray
2019-06-06 9:40 ` Dan Carpenter
2019-06-13 9:15 ` Andrew Murray
2019-06-06 14:39 ` Dan Carpenter
2019-06-13 10:40 ` Andrew Murray
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=20190606101509.GY24680@kadam \
--to=dan.carpenter@oracle.com \
--cc=andrew.murray@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.