From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] IOHDRSZ
Date: Thu, 4 Apr 2013 16:49:08 -0400 [thread overview]
Message-ID: <0b2786f721d464915432e88eed91c18f@ladd.quanstro.net> (raw)
In-Reply-To: <CAOw7k5hNYLF-B=MnGaKejUM97E2Q5MASANP2EnEJzpi-yyPvMQ@mail.gmail.com>
> 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.
i'm thinking of applications that have a seperate buffer for data.
in this case, i can't think of a clean way of sizing that seperate buffer
correctly. if msize=bufsize+IOHDRSZ, then incoming bytes would
be too big.
- erik
prev parent reply other threads:[~2013-04-04 20:49 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
2013-04-04 20:49 ` erik quanstrom [this message]
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=0b2786f721d464915432e88eed91c18f@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--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).