Commits
- Commit:
b3ed4134c8a8c85c9bcd7f1055e35bc8fca7006c
- From:
- cage <cage@invalid>
- Date:
- [regress-extra] refactored test related to file moving or truncation.
- Commit:
f55ab68b8ccd0c8d7fe509f6949f6e65bf77c93b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
9pclib: send size in wstat
This is the counterpart for the recent kamid commit about wstat: we're
lacking the leading size field.
- Commit:
9029ac6f3c1fa3e42c6fa231f8a45ed05d68b61e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
wstat: missing read for size
9p stat message have a leading 2 bytes long size field. It's meant to
simplify the parsing, because while reading the contents of a
directory it's necessary to know how much long an entry is, so the
length field is present even in the Rstat reply and in the Twstat
input.
Previously we didn't consume that bit and thus mis-read all of the
following fields.
- Commit:
6d3d71a91bb82be60ffc572865e4329c40215dfe
- From:
- Omar Polo <op@omarpolo.com>
- Date:
kamid: simplify "not a directory" check
- Commit:
893d3be62b9d01411dcd1bc792aca3f9d01039ee
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix compilation: struct np_stat is defined in kami.h
- Commit:
0e1e2f455e2b0fb9ca77afd4d89bd0ba33ca831a
- From:
- cage <cage@invalid>
- Date:
- [regress-extra] added test for checking truncation of files using Twstat.
- Commit:
f4ad0146e973695127d1c9e1769cd2a7882184d8
- From:
- Omar Polo <op@omarpolo.com>
- Date:
work around wstat limitation
the previous commit added an explicit check for extra data in
messages. The problem is that wstat voluntarily skips reading some
fields at the end, so the len will always be greater than zero!
- Commit:
bcdb46a77ed7b4ff4d9e7ca8fae79fec74b504ae
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fail if the received packet is too long
This adds extra checks to every t* function: if the client sent too
much data per message, treat is an a protocol violation and terminate
the connection. Regress suite still passes, this is just an extra
safety check for finding wrong clients implementations.
The twrite function was the only one with a check like this.
- Commit:
ae6f257a8d22174cb2326cd60d690cceea59fa8e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix np_read{8,16,32,64} functions
they should return 0 on failure, not -1
- Commit:
46e4e74b0a512a6d37edcb8c711bc972f0adc908
- From:
- Omar Polo <op@omarpolo.com>
- Date:
kamid: change fid fname size to NAME_MAX
the fname field is just the file name, so NAME_MAX is more
appropriate.
Committing this separately from the rename change so it's easier to
roll back eventually.
- Commit:
543fc013a4eb973fc1249d5c6d06a0f27903399a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
kamid: rename field fpath to fname
it's actually just the file name, not a path
- Commit:
7d4a725de691bed2059e9b23ffc89aa0e38e113e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fmt
- Commit:
13b8bb0ac6e2a739a68a6d0cb9c96973e6a5f3e5
- From:
- Omar Polo <op@omarpolo.com>
- Date:
ftp: document rename
- Commit:
a9288ad988ac0f49b12cccac801beadd23e68733
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix ls: don't hardcode fid=1
- Commit:
8d8fb849cf1470dfafdb8a5cc598aa510fb8e5c6
- From:
- Omar Polo <op@omarpolo.com>
- Date:
ftp: add nextfid to find the next lower free fid