linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "dan carpenter" <error27@email.com>
To: green@namesys.com
Cc: linux-kernel@vger.kernel.org, smatch-discuss@lists.sf.net
Subject: Re: smatch update / 2.5.64 / kbugs.org
Date: Fri, 07 Mar 2003 01:45:35 -0500	[thread overview]
Message-ID: <20030307064535.20769.qmail@email.com> (raw)

From: Oleg Drokin <green@namesys.com>
> > The smatch bugs for kernel 2.5.64 are up.  The 
> > new url for the smatch bug database is http://kbugs.org.  
> 
> Unfortunatelly the bug database does not work. I mean I cannot connect to it.
> 

Crap...  sorry about that, I screwed up.

> This script can produce a lot less false positives with even more custom merge rules.
> Here's the diff that if run on fs/ext3/super.c from current bk tree, produces
> only one true bug. (your version from cvs produces one real bug and two false positives)
> (8 less hits on my default build).

I have uploaded your modifications to CVS.  I'll use it 
on the next kernel release.  The unfree.pl was just a few
modifications to the deference_check.pl so your patch
will cut down on the false positives with that also.

thanks,
dan carpenter


-- 
_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

Meet Singles
http://corp.mail.com/lavalife


             reply	other threads:[~2003-03-07  6:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07  6:45 dan carpenter [this message]
2003-03-07  6:53 ` smatch update / 2.5.64 / kbugs.org Oleg Drokin
2003-03-14  8:25   ` Oleg Drokin
  -- strict thread matches above, loose matches on Subject: below --
2003-03-07  8:32 dan carpenter
2003-03-06  8:15 dan carpenter
2003-03-06  7:37 dan carpenter
2003-03-06  7:42 ` Greg KH
2003-03-06 15:37 ` Oleg Drokin

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=20030307064535.20769.qmail@email.com \
    --to=error27@email.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smatch-discuss@lists.sf.net \
    /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).