public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Werner Almesberger <wa@almesberger.net>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: Carl Spalletta <cspalletta@yahoo.com>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@transmeta.com>,
	Dan Carpenter <d_carpenter@sbcglobal.net>
Subject: Re: inventing the wheel?
Date: Fri, 30 May 2003 11:30:09 -0300	[thread overview]
Message-ID: <20030530113009.A1667@almesberger.net> (raw)
In-Reply-To: <3ED3E224.1000402@gmx.net>; from c-d.hailfinger.kernel.2003@gmx.net on Wed, May 28, 2003 at 12:09:40AM +0200

Carl-Daniel Hailfinger wrote:
> Now we only need one additional tool to *prove* correctness of the
> kernel ;-)

Perhaps another interesting approach for such source code analyzers
would be to take a top-down view, i.e. assume a certain functional
structure, and check that all the elements are there and in the
right order.

This should be feasible for code that basically follows a certain
template, e.g. network card drivers.

This would also help with the update problem of "fill in the blanks"
type of templates, i.e. if the template changes or is augmented,
some drivers using it may no longer conform to it.

Such a top-down view could be layered on top of a bottom-up analyzer,
e.g. by - manually or automatically - translating some "skeleton"
into a set of rules of the type "if you've called X, you must later
call Y", etc.

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/

  parent reply	other threads:[~2003-05-30 14:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27 18:05 inventing the wheel? Carl Spalletta
2003-05-27 22:09 ` Carl-Daniel Hailfinger
2003-05-28 12:28   ` Carl Spalletta
2003-05-30 14:30   ` Werner Almesberger [this message]
2003-05-30 15:12     ` Richard B. Johnson
2003-05-30 15:26       ` Werner Almesberger

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=20030530113009.A1667@almesberger.net \
    --to=wa@almesberger.net \
    --cc=c-d.hailfinger.kernel.2003@gmx.net \
    --cc=cspalletta@yahoo.com \
    --cc=d_carpenter@sbcglobal.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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