Commits
- Commit:
063e17c1f0daae02711cf135c2bb35dff01c6d91
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add a todo file
- Commit:
5f362b7f054ee9e876d7b8c208fcc09b2235091f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
typo spotted by cage, thanks!
- Commit:
c0ae57b900c0dda41d12793b7a0480159f2946ca
- From:
- Omar Polo <op@omarpolo.com>
- Date:
initialize evbuffer only for dirs
- Commit:
baa405044968a73fd6a257a3504efe7dc5fe7443
- From:
- Omar Polo <op@omarpolo.com>
- Date:
first half of the tread implementation done, no new tests yet
- Commit:
d4e438158258d53a0d22189b432537b22300dd2e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
allow opening directories (for reading only)
- Commit:
7abcb0db7fc2702872e6c25fa74c412d21d58893
- From:
- Omar Polo <op@omarpolo.com>
- Date:
make the compiler happy
- Commit:
250220f1325224c083bce598a4769d84d76b373a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add two open-related tests
- Commit:
99a435901454cc6ca529a783486c83ffddadb110
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix walk fid check: look at fd not iomode to see if it was opened
- Commit:
87a818e80dd7b59d2ee3f9b1cdffc82d7c5c1b4c
- From:
- Omar Polo <op@omarpolo.com>
- Date:
ensure we don't call openat(2) with "" as path
- Commit:
cf758c3329364c1516e2b78c573d6901843bc670
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix Tattach handling
The previous implementation assumed that you can't attach more than
once. This is clearly wrong, Tattach and Twalk are the two ways to
obtain new fids.
This drops the error on subsequential attach and making the test
"multiple attach" passes.
- Commit:
a47c234bedbcc16108a0e4f03b6f333ef72729c8
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add a test that calls attach multiple times
- Commit:
32b8add4cfa7e7c66ac6be38b2cc956880dde08c
- From:
- Omar Polo <op@omarpolo.com>
- Date:
support running only a subset of the tests using a matching pattern
- Commit:
30d22cc724c2dab1c94046e33c729ed24f591b94
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add documentation for the mentioned messages types
- Commit:
4ed3f1b849c58522df2c0f3b1d62ad17d46df479
- From:
- Omar Polo <op@omarpolo.com>
- Date:
cosmetic change: "X/Y passed" instead of "passed X/Y"
- Commit:
3242c0bccce6e6d431c59b04e2cd955e732fa074
- From:
- Omar Polo <op@omarpolo.com>
- Date:
don't let nwqid become negative
at the start of the loop nwqid is 0, so if the first component can't be
opened nwqid becomes -1 and since it's not 0, we end up calling np_walk
with -1 as length. This in turns converts it back to uint16_t and we
generate an invalid packet.
The solution is to not decrement nwqid at all, it fixes all the current
tests case and is the correct behaviour that the rest of the code
expects.