Commits
- Commit:
cab30d8aa7b54656ecc26710b5942cd9578d909c
- From:
- Omar Polo <op@omarpolo.com>
- Date:
document wstat
- Commit:
2254cace9c3b8b5240b19e60f6358902b05c56ea
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add a note about the `size' field in stat
- Commit:
ea9dc606566590242ebe4279bc4ba081990b1d5f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
shrink stat table listing
- Commit:
344d2bade53f42086e3ddc0054a7a82b2a2efe9a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
9pclib: fix qid serialization
twstat was serializing the qid in the wrong order. While here, add a
comment before the qid definition too.
- Commit:
16f1f3bfff8671ebbfd9b69928b9427a7fe1fc8a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
ftp: truncate the file in woc_file
The idea behind woc_file is to create or open a file, but it's always
used for writing fresh new content, so it's actually an error that it
opens a file for writing without truncating it too. It means that if we
write less content than what the file already has, we kepp garbage at
the end.
This adds an extra argument in send_fid (that is actually used only from
woc_file now) so that we can pass KOTRUNC for do_open.
- Commit:
5fe03b5c1758571edfaaa4bef8ebb82245f40618
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix memory leak in walk_path error path
found by clang' static-analyzer
- Commit:
fb7e601b36015a46dc007f114e42f550ddf8a774
- From:
- cage <cage@invalid>
- Date:
- [regress-extra] added testing for changing atime and mtime using wstat.
- 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.