Michael Frey

This issue probably also applies to other logging mappings in ccn-lite.

I think we should stick with "NULL" as a return value and simply remove all parts of the code which pass clearly "NULL" to the function. Any thoughts?

I've removed the "bug" label. I think that the function is simply applied in a wrongful way. A developer should check if the function returns NULL before simply passing it...

This probably would also ease our efforts to get rid of ``malloc`` for IoT devices (by having a component which provides data structures which have been "statically allocated").

> Can you explain the point with the management funcitons with more details. I did not get, why they are related to the content store? Management functions is probably a...

> I am sure we can find a solution for that without introducing mutexes, though. You mean a lock-free memory allocator which allocates memory from a pre-defined memory block?

> sounds like malloc to me (: I'm not an expert on lock-free memory allocation, but I've thought it's a bit more complex (see also [Scalable Lock-Free Dynamic Memory Allocation](https://www.research.ibm.com/people/m/michael/pldi-2004.pdf))

> the first thing would be to evaluate, if there are any calls to _path_detailed() from API functions. If not, then there's no ürpblem at all. git grep to the...

tl;dr i'm happy that you address potential issues with multi-threading and we should keep this in mind We've discussed the parallel access issue during our last project meeting in Hamburg...

> From the perspective of RIOT, making the forwarder multi-threaded is probably a no-go. Making the API calls thread-safe is however necessary, be it for RIOT or Linux/OSX The API...