Skip to contentSkip to conversation

opendir() on a file???

DISCUSSION Jon Masters 3 participants 4 messages Mar 9, 2010

lore
Share & tools
lore
#0 lore raw

Folks,

Now I might be missing something, and I know I'm behind on LKML[0], but the following isn't supposed to work in my book:

/*
* Weird kernel test
*/

#include <sys/types.h>
#include <dirent.h>
#include <stdio.h>

int main(int argc, char **argv)

{
        DIR *dir;

        dir = opendir("foo.conf");

        if (dir)
                printf("WTF?\n");

        return 0;
}

This is on an ext4 filesystem, whereas on a box with an older kernel this test correctly does not print "WTF?". I know some filesystems experiment with streams and treating files as directories, etc. but I wasn't aware that anything particular had changed recently?

The box is running almost an upstream kernel, and I can poke if I'm told this not intended: 2.6.34-0.8.rc0.git11.fc14.x86_64.

What am I missing?

Jon.

[0] The podcast isn't dead, I'm just suffering from a cold and will be taking a day off to recover and catch up with that sometime today.

#1 lore raw
Quoted 2 lines · Jon Masters

Now I might be missing something, and I know I'm behind on LKML[0], but the following isn't supposed to work in my book:

Al introduced and fixed the problem, from what I've seen.

#2 lore raw
Quoted 5 lines · Ulrich Drepper
Quoted 2 lines · Jon Masters

Now I might be missing something, and I know I'm behind on LKML[0], but the following isn't supposed to work in my book:

Al introduced and fixed the problem, from what I've seen.

Thanks. It's fixed in today's rawhide.

Jon.

#3 lore raw
In reply to Jon Masters
Quoted 33 lines · On Tue, 09 Mar 2010 04:26:57 -0500 Jon Masters <[email protected]> wrote:

Folks,

Now I might be missing something, and I know I'm behind on LKML[0], but the following isn't supposed to work in my book:

/*
* Weird kernel test
*/

#include <sys/types.h>
#include <dirent.h>
#include <stdio.h>

int main(int argc, char **argv)

{
        DIR *dir;

        dir = opendir("foo.conf");

        if (dir)
                printf("WTF?\n");

        return 0;
}

This is on an ext4 filesystem, whereas on a box with an older kernel this test correctly does not print "WTF?". I know some filesystems experiment with streams and treating files as directories, etc. but I wasn't aware that anything particular had changed recently?

The box is running almost an upstream kernel, and I can poke if I'm told this not intended: 2.6.34-0.8.rc0.git11.fc14.x86_64.

Quoted 8 lines

What am I missing?

Jon.

[0] The podcast isn't dead, I'm just suffering from a cold and will be taking a day off to recover and catch up with that sometime today.

perhaps you are missing this patch:
commit 781b16775ba0bb55fac0e1757bf0bd87c8879632

Author: Al Viro <[email protected]>
Date:   Sat Mar 6 18:41:07 2010 +0000

Fix a dumb typo - use of & instead of &&

We managed to lose O_DIRECTORY testing due to a stupid typo in commit 1f36f774b2 ("Switch !O_CREAT case to use of do_last()")

but this is only a guess...

cheers,
Flo