Commits
- Commit:
4e7aba8ffdd8756bf7af73dfb5d8b0efa01ce9c1
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix parsing of Twstat
- Commit:
bee0a9e34b2c6fe77faf0c10b8f29a9d6cac611b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
stat: fix `mode' format
Select only the lower two and set the correct bit for directory entries.
While the lower two bytes seems to behave just as on UNIX, the upper
ones don't (at least on OpenBSD.)
- Commit:
91f48e256d92ce302b75d6cc208c09d4aaac5377
- From:
- Omar Polo <op@omarpolo.com>
- Date:
serialize_stat: fix overflow check, report failure
- Commit:
ff6f19b17c7e1d33ec438ee331f1aa3080903acd
- From:
- Omar Polo <op@omarpolo.com>
- Date:
don't expose the "." ad ".." directory entries
- Commit:
73df5ca20482f34c0746b61d2c9fd6e43f3477f8
- From:
- Omar Polo <op@omarpolo.com>
- Date:
Tattach: handle aname ""
9front uses aname "" during Tattach, at least with 9fs without special
arguments, so convert it to our current representation.
- Commit:
70540bb5c2f5f14c96619bdbfb2bd2637e1db586
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix format of Rstat
`count' should be a 2-byte (16-bit) value and we're not neither
accounting for it nor sending it.
- Commit:
865dd3238a329a69864b4b9686567aa056d91c66
- From:
- Omar Polo <op@omarpolo.com>
- Date:
client_send_listener: send correct peerid
fix typo in previous commit where `0' was used instead of peerid.
Spotted by cage, thanks!
- Commit:
5c69b561db9f5713670e2f1e1519cc7f61b06645
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add IMSG_CTL_DEBUG to debug the opened fid
meant to be used from kamictl to dump all the opened fid by every
connection.
- Commit:
982f38dc950a803ee7331eba9f6b6f7a37d45f58
- From:
- Omar Polo <op@omarpolo.com>
- Date:
listener: handle IMSG_CTL_LOG_VERBOSE
adjust the logging level and forward it to every client process so they
can do so too.
- 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:
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.