From: "roger peppe" <rogpeppe@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] infrequent panics
Date: Thu, 13 Mar 2008 10:44:19 +0000 [thread overview]
Message-ID: <df49a7370803130344g6e68b315nd773836ab7383dd6@mail.gmail.com> (raw)
In-Reply-To: <ee9e417a0803121733k71b2940v9afb6bc804d6320b@mail.gmail.com>
> There's already something wrong here -- if spec contains bad
> UTF then buf will overflow all the time.
that's a good gotcha! i'd have naively assumed that
sprint(buf, "%s", s) was equivalent to strcpy(buf, s).
i wonder how many other bits of code are potentially broken because
of this.
next prev parent reply other threads:[~2008-03-13 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 20:08 erik quanstrom
2008-03-13 0:33 ` Russ Cox
2008-03-13 10:44 ` roger peppe [this message]
2008-03-13 2:14 erik quanstrom
2008-03-13 5:57 Brian L. Stuart
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=df49a7370803130344g6e68b315nd773836ab7383dd6@mail.gmail.com \
--to=rogpeppe@gmail.com \
--cc=9fans@9fans.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).