From: Dan Carpenter <dan.carpenter@oracle.com>
To: Himanshu Jha <himanshujha199640@gmail.com>
Cc: smatch@vger.kernel.org, Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: Smatch context checking feature ?
Date: Tue, 4 Jun 2019 14:35:42 +0300 [thread overview]
Message-ID: <20190604113541.GT24680@kadam> (raw)
In-Reply-To: <20190603112925.GA3244@himanshu-Vostro-3559>
On Mon, Jun 03, 2019 at 04:59:25PM +0530, Himanshu Jha wrote:
> Hi,
>
>
> I started to look at the context checking feature of smatch
> in check_locking.c
>
> Honestly, I'm not planning to deep-dive into the codebase
> and rather planning to test its capability. I have already
> tested sparse context imbalance but the problem with smatch
> is that I can't run it on a simple C test program.
>
> I tried the following:
>
> ~/progs/smatch/devel/smatch_scripts/kchecker test.c
>
The way to test is probably:
cp validation/sm_locking4.c test.c
./smatch -p=kernel test.c
> Does building cross function database help in context checking ?
Unfortunately the locking check is too out of date and doesn't take
advantage of the cross function DB.
> I have low spec machine(4GB RAM + 1TB HDD + i5) and IIRC when I
> tried smatch an year ago, rebooting was the only solution as it used
> hang.
That's really small but hopefully it doesn't still lock up. :/ If it
does let me know and I will fix it.
>
> Also, I couldn't find the smatch archive(if there is any). The ones
> on sourceforge does not seem to be maintained ?
https://repo.or.cz/w/smatch.git
regards,
dan carpenter
prev parent reply other threads:[~2019-06-04 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 11:29 Smatch context checking feature ? Himanshu Jha
2019-06-04 11:35 ` Dan Carpenter [this message]
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=20190604113541.GT24680@kadam \
--to=dan.carpenter@oracle.com \
--cc=himanshujha199640@gmail.com \
--cc=lukas.bulwahn@gmail.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 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).