aboutsummaryrefslogtreecommitdiffstats
path: root/src/lib/nfs/Connection.hxx (unfollow)
Commit message (Collapse)AuthorFilesLines
2014-12-15lib/nfs/Connection: implement mount timeoutMax Kellermann1-2/+7
2014-12-15lib/nfs/Connection: add debug flag "in_destroy"Max Kellermann1-0/+5
2014-12-14lib/nfs/Connection: fix memory leak (and assertion failure)Max Kellermann1-0/+7
nfs_destroy_context() will invoke all pending callbacks with err==-EINTR. In CancellableCallback::Callback(), this will invoke NfsConnection::DeferClose(), which however is only designed to be called from nfs_service(). In non-debug mode, this will leak memory because nfs_close_async() is never called. Workaround: before nfs_destroy_context(), invoke nfs_close_async() on all pending file handles.
2014-12-14lib/nfs/Connection: move code to Service()Max Kellermann1-0/+5
2014-12-14lib/nfs/Connection: move code to method InternalClose()Max Kellermann1-0/+5
2014-12-14lib/nfs/Connection: make in_service and in_event debug-only flagsMax Kellermann1-0/+2
2014-10-07lib/nfs/Connection: add methods {Open,Read,Close}Directory()Max Kellermann1-0/+10
2014-10-07lib/nfs/Connection: add method Stat(path)Max Kellermann1-0/+3
2014-10-06lib/nfs/Connection: make GetEventLoop() publicMax Kellermann1-4/+4
2014-10-01lib/nfs/FileReader: postpone the nfs_close_async() callMax Kellermann1-1/+32
If an async opertion is in progress, nfs_close_async() will make libnfs crash because the RPC callback will dereference an object that was freed by nfs_close_async().
2014-10-01lib/nfs/Connection: fix memory leak when cancelling Open()Max Kellermann1-2/+12
Close the newly allocated file handle passed to the callback.
2014-10-01lib/nfs/Connection: remove MutexMax Kellermann1-3/+0
All locks are currenly held from only a single thread (the IOThread) and thus we don't need the Mutex.
2014-10-01lib/nfs/Connection: add method GetEventLoop()Max Kellermann1-0/+4
2014-10-01lib/nfs/Connection: remove obsolete flag postponed_destroyMax Kellermann1-9/+1
2014-10-01lib/nfs/Connection: remove deprecated move constructor workaroundMax Kellermann1-16/+0
Not used anymore because NfsManager now uses boost::intrusive::set instead of std::map.
2014-10-01lib/nfs/Glue: destruct the NfsManager in the I/O threadMax Kellermann1-0/+3
This allows eliminating the indirection code from the NfsConnection destructor.
2014-10-01lib/nfs/Cancellable: use boost::intrusive::listMax Kellermann1-2/+2
Reduce Remove() overhead because we don't have to walk the list to find an iterator by reference.
2014-06-17lib/nfs/Manager: gcc 4.7 compatibility hackMax Kellermann1-0/+16
std::map::emplace() is only available from gcc 4.8 on.
2014-06-17input/nfs: use the asynchronous libnfs APIMax Kellermann1-0/+160
More robust and cancellable.