From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Bugs in V6 'dcheck'
Date: Sun, 1 Jun 2014 23:18:07 -0400 (EDT) [thread overview]
Message-ID: <20140602031807.8B4DC18C0AD@mercury.lcs.mit.edu> (raw)
> From: "Ron Natalie" <ron at ronnatalie.com>
> The variable in question was a global static, 'ino' (the current inode
> number),
> Static is a much overloaded word in C, it's just a global variable.
Sorry; I was using 'static' in the general CS sense, not C-specific!
> in the version 7 version of icheck .. they appear to have fixed it.
Actually, they seem to have got all three bugs I saw (including the one I
hadn't actually experienced yet, which would cause a segmentation violation).
> From: Tim Newsham <tim.newsham at gmail.com>
> There are bugs to be found .. Here are some more (security related, as
> thats my inclination):
> ...
> http://minnie.tuhs.org/pipermail/unix-jun72/2008-May/000126.html
Fascinating mailing list! Thanks for the pointer.
Noel
next reply other threads:[~2014-06-02 3:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 3:18 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-03 17:33 Nelson H. F. Beebe
2014-06-02 3:34 Noel Chiappa
2014-06-02 4:05 ` Mary Ann Horton
2014-06-02 6:12 ` arnold
2014-06-03 12:11 ` emanuel stiebler
2014-06-02 2:14 Michael Spacefalcon
2014-06-02 2:51 ` John Cowan
2014-05-31 23:24 Doug McIlroy
2014-06-01 0:17 ` Kevin Schoedel
2014-06-01 22:54 ` scj
2014-06-01 23:48 ` A. P. Garcia
2014-06-02 1:11 ` Ronald Natalie
2014-06-02 2:10 ` A. P. Garcia
2014-06-03 16:38 ` Nelson H. F. Beebe
2014-05-31 15:55 Noel Chiappa
2014-05-31 16:18 ` Ron Natalie
2014-05-31 14:19 Noel Chiappa
2014-05-31 13:30 Norman Wilson
2014-05-31 16:03 ` John Cowan
[not found] ` <20140531161620.GL28034@mcvoy.com>
2014-05-31 17:16 ` John Cowan
2014-05-31 13:15 Noel Chiappa
2014-05-31 13:23 ` Ronald Natalie
2014-05-31 18:58 ` Tim Newsham
2014-05-31 19:48 ` Clem Cole
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=20140602031807.8B4DC18C0AD@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.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 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).