Of if you're dealing with a sane filesystem append '/.' and it should be
safe anywhere. The only difference is that you'll get EPERM in the
strange case of a readable-but-not-searchable directory. Not a great
loss for most applications.
> Finally, I should probably just add a "opendir()" system call. That way
> I could return EISDIR for normal open() calls some day in the future
> when we can drop the old binary support. Consider it done.
Are you sure there's a distinct advantage over just making another flag to
open (and having libc's opendir pass that in?) Seems to me that the
sys_opendir syscall will be almost the same code as sys_open anyway...
-Mitch
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/