Fix Prevent issue

Fix Prevent issue

- Incorrect usage of TEMP_FAILURE_RETRY

[Issue#]   CID: 22993, 22996, LINUXWRT-906
[Problem]  closedir() repeated if EINTR occurrs
[Cause]    Same as Prevent CID: 22995
           https://review.tizendev.org/gerrit/#/c/83449/

  * For POSIX closedir() specifies two possible errno values: EBADF, EINTR
    (see closedir(3p)).
  * For Linux, on the other hand, only one errno value is specified: EBADF
    (see closedir(3)).
  * In fact, closedir() implementation in GNU C Library may set other errno
    values as well, e.g. EINVAL if value NULL is passed to the function
    (verified for glibc 2.15, source file sysdeps/unix/closedir.c).

  * Assuming that closedir() is just a wrapper around a call to close()
    system call and having in mind that it was decided (and confirmed by
    Linus Torvalds) that repeating close() even for EINTR is unsafe which I have
    decided to not repeat closedir() in such case as well.

  * What's more, implementation of closedir() in GNU C Library calls free()
    on the stream handle, so repeating closedir() may lead to memory
    corruption (as reported by Prevent).

[Solution] Do not repeat closedir() on error (even EINTR).

[SCMRequest] N/A
[Verification] Build repository.

Change-Id: I857861d1f10954d4c199bf8d54fc5ea13cb00d44