9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] IOHDRSZ
Date: Thu,  4 Apr 2013 21:14:08 +0100	[thread overview]
Message-ID: <CAOw7k5hNYLF-B=MnGaKejUM97E2Q5MASANP2EnEJzpi-yyPvMQ@mail.gmail.com> (raw)
In-Reply-To: <1d60ad5fac2f22abe5687a2325ab9c63@ladd.quanstro.net>

[-- Attachment #1: Type: text/plain, Size: 346 bytes --]

On 4 April 2013 20:50, erik quanstrom <quanstro@quanstro.net> wrote:

> so
> i think this assumption is going to lead to
> 6-byte buffer overruns.
>

I don't follow the reasoning. bufsize + Rread or Twrite will always fit.
bufsize is the limit for application data. The receiving 9P also trims the
count
to match the receiving buffer.

[-- Attachment #2: Type: text/html, Size: 772 bytes --]

  reply	other threads:[~2013-04-04 20:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 19:50 erik quanstrom
2013-04-04 20:14 ` Charles Forsyth [this message]
2013-04-04 20:49   ` erik quanstrom

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='CAOw7k5hNYLF-B=MnGaKejUM97E2Q5MASANP2EnEJzpi-yyPvMQ@mail.gmail.com' \
    --to=charles.forsyth@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).