Commits
- Commit:
eda58043e1952b4ce7f49c1c7a22e4f4287bf1d4
- From:
- Omar Polo <op@omarpolo.com>
- Date:
kamid: include grp.h for setgroups on linux
- Commit:
315668d47de15aca3c4f52136a3e55cd2adc04dd
- From:
- Omar Polo <op@omarpolo.com>
- Date:
endian.h is not universally available
FreeBSD and NetBSD have sys/endian.h, on MacOS we need to use the
functions from libkern/OSByteOrder.h
see github issue #1
- Commit:
ec5d75ef0eb4b9bfe701449ba0d58b281229f7c9
- From:
- Omar Polo <op@omarpolo.com>
- Date:
simplify check in handle_message
- Commit:
f9d8661b68f61636701e3320cafaf5853db70123
- From:
- Omar Polo <op@omarpolo.com>
- Date:
report the correct write length
- Commit:
66926cfc3a240fee6da318457f40e62cc246fdc9
- From:
- Omar Polo <op@omarpolo.com>
- Date:
allow jumbo reads
- Commit:
23fbe390bd2006b2da54d7ed1fdd5e9615e58d4b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
allow Tread to fill a message
a message of `msize' len is valid, we just need to make sure to _not_
overflow it.
- Commit:
a9eb1af3d081c65f002dfa7e3cde71e3cc23e963
- From:
- Omar Polo <op@omarpolo.com>
- Date:
allow jumbo Twrites for real
- Commit:
fbeaf87b54479383a77dc1fc41318bb788267154
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fail on "jumbo" requests (except for Twrite)
except for Twrite, all other requests are passed via a single imsg.
We don't handle "jumbo" request for anything outside Twrite, nor it
does make sense actually, so let's drop it.
(well, for Twstat an argument can be made, maybe)
- Commit:
182b48dc821a0a4cf7bbcfcdf5f9d376136fd7e6
- From:
- Omar Polo <op@omarpolo.com>
- Date:
proper err handling for parse_message
- Commit:
8b0a506230428aaacefd78995955e80f058d9c9d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
allow Twrite with size bigger than ~16K
Until now I've been using a single imsg to handle each messages and
the imsg framework has a limit of around 16K for message. For almost
all requests, this is fine.
Except for Twrite and Tread.
This is an attempt to make Twrite handle bigger buffers. The listener
process just looks at how big a request is and split it up in multiple
messages and the client process tries to remember the fid, position
and missing data to continue the write. This means that a single
Twrite can be split up in multiple write(2)s.
- Commit:
6be59daa956c266ddcbb86bdf8efc0d34438291b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
reject connections with an msize ridiculously small
- Commit:
b7c2d37758810d5071d57f6769bacdc53c1d2e61
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix twstat handling of mode bits
twstat was truncating out the user mode bits. Found the hard way by
cage.
- 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