From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Bounds checking bug ifcall(2) functions
Date: Fri, 16 Nov 2007 10:18:54 +0000 [thread overview]
Message-ID: <473CA225.86119D3C@null.net> (raw)
In-Reply-To: <815f4e4b0711091501v53a37569x5c5f576623fb9547@mail.gmail.com>
Erik Dalén wrote:
> On second thought I think you are correct. At the end of the function
> the pointer might be one byte past the buffer size, but then it won't
> do any reads or writes (But it could be a problem if the buffer is
> right at the end of the virtual memory space :).
The C standard requires that pointer arithmetic work properly
for one-past-the-end pointers. On some architectures that may
mean that each data segment has to have an extra (unused) byte
allocated, but on most architectures nothing special has to be
done.
next prev parent reply other threads:[~2007-11-16 10:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 22:20 [9fans] Bounds checking bug in fcall(2) functions Erik Dalén
2007-11-09 22:42 ` Charles Forsyth
2007-11-09 23:01 ` Erik Dalén
2007-11-09 23:41 ` Charles Forsyth
2007-11-10 17:55 ` Russ Cox
2007-11-16 10:18 ` Douglas A. Gwyn [this message]
2007-11-16 10:38 ` [9fans] Bounds checking bug ifcall(2) functions erik quanstrom
2007-11-19 10:14 ` Douglas A. Gwyn
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=473CA225.86119D3C@null.net \
--to=dagwyn@null.net \
--cc=9fans@cse.psu.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).