Commits


ensure that a walk with zero paths don't replies with a qid A walk of zero paths is used to duplicate a fid. it doesn't make sense to reply with a body containing the qid relative to the file, because it's not a real walk, it's just a duplication. Furthermore, it would break the expectations that the number of qid returned is less or equal to the walked components.


Tcreate: check against ".", ".." and files with `/' in them.


Merge branch 'main' of ssh://omarpolo.com/kamid


- [regress-extra] added test for tCreate, both file and directory.


implement Tremove


typo


implement Tcreate


implement Tstat


drop extra do_send


fix typo. spotted by cage, thanks!


implement Twrite


allow directory to be read again using offset 0 The documentation says explicitly that the offset is *either* 0 or the last offset plus count; that means that after some read a client can require *again* an offset 0 (i.e. doing a rewinding the directory.)


implement Tread against directories To do so it was needed to modify the np_* functions so they take an explicit evbuffer.


PATH_MAX already accounts for NUL


free evp only if it was allocated apparently, evbuffer_free doesn't like NULLs