All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Marion & Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: smatch@vger.kernel.org
Subject: Re: [RFC PATCH] check_freeing_devm: Also track erroneous usage of kfree when the pointer has been re-assigned
Date: Thu, 26 May 2022 15:00:16 +0300	[thread overview]
Message-ID: <20220526120016.GE2168@kadam> (raw)
In-Reply-To: <eed02978-bf56-428e-29ed-78a3d9f5b706@wanadoo.fr>

On Thu, May 26, 2022 at 01:40:51PM +0200, Marion & Christophe JAILLET wrote:
> 
> Le 26/05/2022 à 13:07, Dan Carpenter a écrit :
> > On Thu, May 26, 2022 at 12:30:05PM +0200, Christophe JAILLET wrote:
> > > Le 26/05/2022 à 11:51, Dan Carpenter a écrit :
> > > > > All I know is that it seams to work for me, even if it has not detected any
> > > > > issue yet :) (compiling takes SO MUCH time on my machine)
> > > > Yeah. :/  How big is your smatch_db.sqlite file?
> > > I don't use any up-to-now.
> > Basically all my changes are targetted at making the smatch_db.sqlite
> > file smaller so they won't help you.  Are you at least doing a parallel
> > build?  The smatch_scripts/test_kernel.sh script does a make -j${NR_CPU}.
> 
> Yep.
> 
> I've also tweaked smatch_scripts/kchecker which doesn't have any -j, IIUC.

Normally, I only use kchecker on one file...  The problem with doing
parallel builds is that you have to print the warnings to a file instead
of to stdout.

regards,
dan carpenter

  reply	other threads:[~2022-05-26 12:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26  7:15 [RFC PATCH] check_freeing_devm: Also track erroneous usage of kfree when the pointer has been re-assigned Christophe JAILLET
2022-05-26  9:51 ` Dan Carpenter
2022-05-26 10:30   ` Christophe JAILLET
2022-05-26 11:07     ` Dan Carpenter
2022-05-26 11:40       ` Marion & Christophe JAILLET
2022-05-26 12:00         ` Dan Carpenter [this message]
2022-05-26 13:37           ` Christophe JAILLET
2022-05-26 13:49             ` Dan Carpenter
2022-05-26 14:22               ` Christophe JAILLET

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=20220526120016.GE2168@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --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.