From: Dawson Engler <engler@csl.Stanford.EDU>
To: jdike@karaya.com (Jeff Dike)
Cc: linux-kernel@vger.kernel.org, mc@cs.Stanford.EDU
Subject: Re: [CHECKER] big stack variables
Date: Thu, 15 Mar 2001 23:19:57 -0800 (PST) [thread overview]
Message-ID: <200103160719.XAA04602@csl.Stanford.EDU> (raw)
In-Reply-To: <200103160256.VAA02335@karaya.com> from "Jeff Dike" at Mar 15, 2001 09:56:10 PM
> engler@csl.Stanford.EDU said:
> > As usual, please report any false positives so we can fix our
> > checkers.
>
> Not a false positive, but a false negative:
>
> the tty_struct locals at lines 1994 and 2029 in tty_register_devfs and
> tty_unregister_devfs, respectively, in the 2.4.2 drivers/char/tty_io.c.
Turns out we didn't have CONFIG_DEVFS_FS defined. Big time fun when it is:
/u2/engler/mc/2.4.1/drivers/char/tty_io.c:1996:tty_register_devfs: ERROR:VAR:1996:1996: suspicious var 'tty' = 3112 bytes
/u2/engler/mc/2.4.1/drivers/char/tty_io.c:2007:tty_register_devfs: ERROR:FN:2007:2007: function stack consumes = 3146 bytes
/u2/engler/mc/2.4.1/drivers/char/tty_io.c:2031:tty_unregister_devfs: ERROR:VAR:2031:2031: suspicious var 'tty' = 3112 bytes
/u2/engler/mc/2.4.1/drivers/char/tty_io.c:2042:tty_unregister_devfs: ERROR:FN:2042:2042: function stack consumes = 3148 bytes
Right now we've just gone in and put =y for all options in .config --- is
there a more principled approach that will get more coverage?
> Nice work, BTW.
Thanks! If you have any other ideas of things to check for, do let us
know. We're mainly just going after things we've found in comments and
code. We have about another 600 potential bugs to report, but are
going over them to try to make sure they are reasonable.
Dawson
next prev parent reply other threads:[~2001-03-16 7:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-16 2:34 [CHECKER] big stack variables Dawson Engler
2001-03-16 2:56 ` Jeff Dike
2001-03-16 3:06 ` Andrew Morton
2001-03-16 7:19 ` Dawson Engler [this message]
2001-03-16 8:23 ` Andrew Morton
2001-03-16 17:57 ` Jeff Dike
2001-03-16 16:58 ` Alexander Viro
2001-03-16 19:37 ` Jeff Dike
2001-03-17 6:01 ` Jeff Dike
2001-03-17 11:39 ` David Weinehall
2001-03-18 17:41 ` Jeff Dike
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=200103160719.XAA04602@csl.Stanford.EDU \
--to=engler@csl.stanford.edu \
--cc=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mc@cs.Stanford.EDU \
/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.