What happened was that one fairly rare case (trying to traverse a
non-existent directory) got the wrong error code. Instead of returning
ENOENT it returned ENOTDIR. And I didn't notice, because it only shows
up if you do something "bad" (but that "bad" thing can most easily be to
run with a bad PATH that contains non-existent directory entries, which
is apparently what a few people had).
Linus
-
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/