Comment 40 for bug 198351

Actually Samba upstream does consider the non-threadsafeness of libsmbclient as a bug, it's just that it's going to take a while to fix it :-).

We're slowly but surely moving towards getting a thread safe libsmbclient, Can't promise when it will be done, but it is our intent to get there.

So at the moment, libsmbclient is not thread safe. So using separate processes in SMBNetFS is the *only* way to safely use libsmbclient, so I'd argue that libsmbclient in this case isn't exactly "buggy", but just not working in the way you want :-).

When we finally announce libsmbclient is thread-safe, and your threaded code using it breaks, *then* you can call it buggy :-). But not before please - unless you have specific single-threaded bugs you know about and need fixing. But if that is the case please report them to bugzilla.samba.org and we'll fix them !

Jeremy.