All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: "Robert T. Johnson" <rtjohnso@eecs.berkeley.edu>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org,
	marcelo@conectiva.com.br, sensors@Stimpy.netroedge.com,
	vsu@altlinux.ru
Subject: [PATCH 2.4] i2c-dev user/kernel bug and mem leak
Date: Thu, 19 May 2005 06:24:15 +0000	[thread overview]
Message-ID: <20030829182132.29c3ac55.khali@linux-fr.org> (raw)
In-Reply-To: <1062033440.16799.22.camel@dooby.cs.berkeley.edu>


> Here's the patch against 2.6.0-test4.  Just to remind everyone, this
> patch doesn't fix any bugs (they're already fixed in 2.6.0-test3), it
> just makes the code pass our static analysis tool, cqual, without
> generating a warning.  Since finding and fixing these bugs is so
> tricky, it seems worthwhile to have code which can be automatically
> verified to be bug-free (at least w.r.t. user/kernel pointers). 
> That's what this patch is about.  Let me know if you have any
> questions or comments. Thanks for everyone's help.

If I read the patch correctly, this is basically a kind of reversal to
your original patch, before Sergey and I changed it?

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <khali@linux-fr.org>
To: "Robert T. Johnson" <rtjohnso@eecs.berkeley.edu>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org,
	marcelo@conectiva.com.br, sensors@Stimpy.netroedge.com,
	vsu@altlinux.ru
Subject: Re: [PATCH 2.4] i2c-dev user/kernel bug and mem leak
Date: Fri, 29 Aug 2003 18:21:32 +0200	[thread overview]
Message-ID: <20030829182132.29c3ac55.khali@linux-fr.org> (raw)
In-Reply-To: <1062033440.16799.22.camel@dooby.cs.berkeley.edu>


> Here's the patch against 2.6.0-test4.  Just to remind everyone, this
> patch doesn't fix any bugs (they're already fixed in 2.6.0-test3), it
> just makes the code pass our static analysis tool, cqual, without
> generating a warning.  Since finding and fixing these bugs is so
> tricky, it seems worthwhile to have code which can be automatically
> verified to be bug-free (at least w.r.t. user/kernel pointers). 
> That's what this patch is about.  Let me know if you have any
> questions or comments. Thanks for everyone's help.

If I read the patch correctly, this is basically a kind of reversal to
your original patch, before Sergey and I changed it?

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

  reply	other threads:[~2005-05-19  6:24 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-03 17:23 PATCH: 2.4.22-pre7 drivers/i2c/i2c-dev.c user/kernel bug and mem leak Jean Delvare
2005-05-19  6:24 ` PATCH: 2.4.22-pre7 drivers/i2c/i2c-dev.c user/kernel bug and Jean Delvare
2003-08-04 15:32 ` PATCH: 2.4.22-pre7 drivers/i2c/i2c-dev.c user/kernel bug and mem leak Sergey Vlasov
2005-05-19  6:24   ` PATCH: 2.4.22-pre7 drivers/i2c/i2c-dev.c user/kernel bug and Sergey Vlasov
2003-08-05  8:32   ` PATCH: 2.4.22-pre7 drivers/i2c/i2c-dev.c user/kernel bug and mem leak Jean Delvare
2005-05-19  6:24     ` PATCH: 2.4.22-pre7 drivers/i2c/i2c-dev.c user/kernel bug and Jean Delvare
2003-08-05 14:10     ` PATCH: 2.4.22-pre7 drivers/i2c/i2c-dev.c user/kernel bug and mem leak Sergey Vlasov
2005-05-19  6:24       ` PATCH: 2.4.22-pre7 drivers/i2c/i2c-dev.c user/kernel bug and Sergey Vlasov
2003-08-05 21:07     ` PATCH: 2.4.22-pre7 drivers/i2c/i2c-dev.c user/kernel bug and mem leak Greg KH
2005-05-19  6:24       ` PATCH: 2.4.22-pre7 drivers/i2c/i2c-dev.c user/kernel bug and mem Greg KH
2003-08-06  8:07       ` [PATCH 2.4] i2c-dev user/kernel bug and mem leak Jean Delvare
2005-05-19  6:24         ` Jean Delvare
2005-05-19  6:24         ` Robert T. Johnson
2005-05-19  6:24         ` Jean Delvare
2005-05-19  6:24         ` Greg KH
2005-05-19  6:24         ` Greg KH
2003-08-15  2:01           ` Robert T. Johnson
2005-05-19  6:24             ` Robert T. Johnson
2003-08-15 21:13             ` Greg KH
2005-05-19  6:24               ` Greg KH
2003-08-15 22:17               ` Robert T. Johnson
2005-05-19  6:24                 ` Robert T. Johnson
2003-08-15 23:51                 ` Greg KH
2005-05-19  6:24                   ` Greg KH
2003-08-18  0:54                   ` Robert T. Johnson
2005-05-19  6:24                     ` Robert T. Johnson
2003-08-18 21:05                     ` Greg KH
2005-05-19  6:24                       ` Greg KH
2003-09-10 23:02                       ` CQual 0.99 Released: user/kernel pointer bug finding tool Robert T. Johnson
2003-08-28  1:17               ` [PATCH 2.4] i2c-dev user/kernel bug and mem leak Robert T. Johnson
2005-05-19  6:24                 ` Robert T. Johnson
2003-08-29 16:21                 ` Jean Delvare [this message]
2005-05-19  6:24                   ` Jean Delvare
2003-08-29 17:30                   ` Robert T. Johnson
2005-05-19  6:24                     ` Robert T. Johnson
2005-05-19  6:24         ` Jean Delvare

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=20030829182132.29c3ac55.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=rtjohnso@eecs.berkeley.edu \
    --cc=sensors@Stimpy.netroedge.com \
    --cc=vsu@altlinux.ru \
    /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.