9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Anthony Martin <ality@pbrane.org>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] 9P reading directories client/server behavior
Date: Tue, 9 Mar 2021 12:01:28 -0800
Message-ID: <YEfUGKqZkZMMlLQu@alice> (raw)
In-Reply-To: <202103091405.129E5mMY002773@sdf.org>

nicolagi via 9fans <9fans@9fans.net> once said:
> The only question that still stands is the last in my original post:
> What happens and what should happen when a dir entry is larger than
> msize-24? Possibly written from a connection with a large msize, and to
> be read from a connection with a smaller msize?

In that case either the server or client lied about it's
msize and is not correctly speaking the 9p protocol.

From version(5):

        The client suggests a maximum message size, msize, that is
        the maximum length, in bytes, it will ever generate or ex-
        pect to receive in a single 9P message. This count includes
        all 9P protocol data, starting from the size field and ex-
        tending through the message, but excludes enveloping trans-
        port protocols. The server responds with its own maximum,
        msize, which must be less than or equal to the client's
        value. Thenceforth, both sides of the connection must honor
        this limit.

Cheers,
  Anthony

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42be63e964005519-Mcceb79ab7dadcad157ebec8a
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2021-03-09 20:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 14:05 nicolagi via 9fans
2021-03-09 20:01 ` Anthony Martin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-10 19:36 nicolagi via 9fans
2021-03-09 13:32 nicolagi via 9fans
2021-04-09 20:00 ` Russ Cox
2021-04-14 18:06   ` nicolagi via 9fans

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=YEfUGKqZkZMMlLQu@alice \
    --to=ality@pbrane.org \
    --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

9fans - fans of the OS Plan 9 from Bell Labs

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.vuxu.org/9fans

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 9fans 9fans/ http://inbox.vuxu.org/9fans \
		9fans@9fans.net
	public-inbox-index 9fans

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.9fans


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git