While there are a few problems around handling of msize, the easiest to address and, arguably, the most problematic is that of Twrite. We now truncate Twrite.Data to the correct length if it will overflow the msize limit negotiated on the session. ErrShortWrite is returned by the `Session.Write` method if written data is truncated. In addition, we now reject incoming messages from `ReadFcall` that overflow the msize. Such messages are probably terminal in practice, but can be detected with the `Overflow` function. Tread is also handled accordingly, such that the Count field will be rewritten such that the response doesn't overflow the msize. Signed-off-by: Stephen J Day <stephen.day@docker.com>

p9p: use new context package throughout

Signed-off-by: Stephen J Day <stephen.day@docker.com>

Fixes the MSize comparison when negociating msize with server

Signed-off-by: Simon Ferquel <simon.ferquel@docker.com>

Specify type for all constants, not just the first

transport: remove race condition on close

Closes #22 Signed-off-by: Dominik Honnef <dominik@honnef.co>

Signed-off-by: Stephen J Day <stephen.day@docker.com>

Fix race-y channel close/error assignment

Fix readme alignment

Data race occurred when assigning to err and then subsequently reading it from anywhere else. Moving the channel close down could potentially help, but far easier to just gate both with a sync.Once since this isn't a code path that seems like it needs to be super-performant. Changes cause CloseWithError to be call-able once, ensuring that there's no case where err is written to while being read (as would happen when closing and reading c.err from another goroutine the moment c.closed is closed). Signed-off-by: Noel Cower <ncower@gmail.com>

Signed-off-by: French Ben <frenchben@docker.com>

Added badge badge

Signed-off-by: French Ben <frenchben@docker.com>