quick-read: Fix dirname(3) usage

glibc dirname() modify the string it is given and returns it.
glusterfs takes this behavior for granted, and assume that if it
gives a malloc'ed string to dirname(), then it can free()) the
return value.

Here is what SUSv2 says:
http://opengroup.org/onlinepubs/007908799/xsh/dirname.html
"The dirname() function may modify the string pointed to by path,
and may return a pointer to static storage"

At least NetBSD returns a static storage. glusterfs will return it to
a calling function that has the responsability to free it, causing
a SIGSEGV.

Thanks to: Emmanuel Dreyfus <manu@netbsd.org>

Change-Id: I8b1b946a005ee487b4b9fb23c0f85a41facfe7c4
BUG: 2923
Reviewed-on: http://review.gluster.com/52
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Anand Avati <avati@gluster.com>

0 files changed, 0 insertions, 0 deletions