[THRIFT-3224] Fix TNamedPipeServer unpredictable behavior on accept

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.9.2
• Fix Version/s: 0.9.3
• Component/s: C++ - Library
• Labels: patch

Environment

Windows

• Patch Info: Patch Available
• Flags: Patch, Important
• Assignee: Paweł Janicki
• Reporter: Paweł Janicki
• Created: 07/Jul/15 11:00
• Updated: 21/Jul/15 02:21
• Resolved: 16/Jul/15 13:15

Description

Application bahavior utilizing TNamedPipeServer is unpredictable due misuse of TAutoHandle.

Project uses TAutoHandle class, an analogy of std::unique_ptr, for managing WIN32 handles. The dangerous members of this concept are: the direct getter "HANDLE TAutoHandle::h" and release method "void __thiscall TAutoHandle::release()"

Below code citation introduces serous bug:

{
    TAutoCrit lock(pipe_protect_);
    GlobalOutput.printf("Client connected.");
    shared_ptr<TPipe> client(new TPipe(Pipe_.h));
    Pipe_.release();
}

The getter is used in TNamedPipeServer::acceptImpl() to pass internal handle value to c-tor of TPipe and just after c-tion HANDLE__thiscall TAutoHandle::release() is called to release ownership. That means the TPipe object is expected to take ownership of the resource, but if TPipe c-tor throws the d-tor of TAutoHandle is called releasing the resource and the incomplete TPipe object does the same. Since now it is impossible to ensure that the second free of the handle value was not performed on a resource that was opened in meantime by other thread.

I propose to solve the issue by ensuring the handle is not owned by two objects at a time.