Checking if a dir. entry returned by readdir is a directory, link or file. dent->d_type isn’t showing the type

by

d_type is a speed optimization to save on lstat(2) calls, when it’s supported.

As the readdir(3) man page points out, not all filesystems return real info in the d_type field (typically because it would take an extra disk seek to read the inode, as is the case for XFS if you didn’t use mkfs.xfs -n ftype=1 (implied by -m crc=1 which is not yet the default). Filesystems that always set DT_UNKNOWN are common in real life, and not something that you can ignore. XFS is not the only example.

You always need code that will fall back to using lstat(2) if d_type==DT_UNKNOWN, if the filename alone isn’t enough to decide it’s uninteresting. (This is the case for some callers, like find -name or expanding globs like *.c, which is why readdir doesn’t incur the overhead of filling it in if it would take an extra disk read.)

The Linux getdents(2) man page has an example program that does what you’re trying to do, including a chained-ternary-operator block to decode the d_type field into text strings. (As the other answers point out, your mistake is printing it out as an character, rather than comparing it against DT_REG, DT_DIR, etc.)

Anyway, the other answers mostly covered things, but missed the critical detail that you NEED a fallback for the case when d_type == DT_UNKNOWN (0 on Linux. d_type is stored in what used to be a padding byte, until Linux 2.6.4).

To be portable, your code needs to check that struct dirent even HAS a d_type field, if you use it, or your code won’t even compile outside of GNU and BSD systems. (see readdir(3))

I wrote an example for finding directories with readdir, using d_type with a fallback to stat when d_type isn’t available at compile time, when it’s DT_UNKNOWN, and for symlinks.

More Related Contents:

  1. Why does stat fail using a name from readdir? [duplicate]
  2. what the output of this code and why?
  3. printf anomaly after “fork()”
  4. How to make child process die after parent exits?
  5. What is time_t ultimately a typedef to?
  6. What is the equivalent to Posix popen() in the Win32 API?
  7. How to recursively list directories in C on Linux?
  8. How does kernel get an executable binary file running under linux?
  9. Measure time in Linux – time vs clock vs getrusage vs clock_gettime vs gettimeofday vs timespec_get?
  10. stdout thread-safe in C on Linux?
  11. Is malloc/free a syscall or a library routine provided by libc?
  12. Creating a new directory in C
  13. Building a kernel module from several source files which one of them has the same name as the module
  14. Turn a simple socket into an SSL socket
  15. What parts of this HelloWorld assembly code are essential if I were to write the program in assembly?
  16. How to check if a given file descriptor stored in a variable is still valid?
  17. Does readdir() guarantee an order?
  18. Are file descriptors shared when fork()ing?
  19. Detecting 64bit compile in C
  20. how to call function in executable from my library?
  21. How does sig_atomic_t actually work?
  22. Interprocess mutex with pthreads
  23. How to make backtrace()/backtrace_symbols() print the function names?
  24. plain C: opening a directory with fopen()
  25. How to make ncurses display UTF-8 chars correctly in C?
  26. Difference between “system” and “exec” in Linux?
  27. What’s a good C decompiler? [closed]
  28. How to set the IP address from C in linux
  29. In C, what’s the size of stdout buffer?
  30. How to print exact value of the program counter in C

Leave a Comment