From: Alex Zarochentsev <zam@namesys.com>
To: Joe Orton <jorton@redhat.com>
Cc: reiserfs-list@namesys.com
Subject: Re: EACCESS vs ENOENT for nonexistent files-within-files
Date: Tue, 14 Sep 2004 00:58:13 +0400 [thread overview]
Message-ID: <20040913205812.GD2252@backtop.namesys.com> (raw)
In-Reply-To: <20040913185255.GA1920@redhat.com>
On Mon, Sep 13, 2004 at 07:52:55PM +0100, Joe Orton wrote:
> On Mon, Sep 13, 2004 at 08:13:26PM +0400, Alex Zarochentsev wrote:
> > On Mon, Sep 13, 2004 at 03:06:37PM +0100, Joe Orton wrote:
> > > Hi, we had a bug report that Apache httpd logs a spurious error for
> > > every file served from a reiser4 filesystem, because httpd assumes that
> > > /path/to/file/.htaccess (where /path/to/file is a normal file) returns
> > > ENOENT or ENOTDIR, but reiser4 returns EACCES in this case.
what does the user get in the browser?
> > >
> > > Can someone explain the justification behind reiser4's behaviour?
> > > httpd's assumption does not seem unreasonable, and EACCES seems to make
> > > little sense for this error case.
> >
> > It is because open(name, O_DIRECTORY) is successful for regular files in
> > reiser4. Once it succedes, Apache2 thinks that is a directory and tries to
> > open .htaccess under it.
>
> I don't think that has anything to do with it. It's a simple open()
> without O_DIRECTORY which is failing with EACCES. The reporter
> confirmed this with the simplest of tests:
>
> $ touch newfile.txt
> $ cat newfile.txt/.htaccess
> cat: newfile.txt/.htaccess: Permission denied
But what is the reason why apache2 looks at <regular file>/.htaccess ?
can you ask the user to add execute permitions (just for test) to the file
and see would apache2 work with the file.
> this is the behaviour I'm trying to find the justification for.
>
> > There are two solutions:
> >
> > 1) mount reiser4 partition with "nopseudo" mount option. it makes /metas/* files
> > unaccessible.
>
> If this is broken by default, our users will continue to complain, so
> that doesn't really help.
>
> > 2) apply the patch:
>
> OK, does this mean you do consider this a bug in reiser4 which will be
> fixed in future releases, then?
it requires Linux VFS changes, the changes are being discussed
in LKML still.
>
> Regards,
>
> joe
--
Alex.
next prev parent reply other threads:[~2004-09-13 20:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 14:06 EACCESS vs ENOENT for nonexistent files-within-files Joe Orton
2004-09-13 14:25 ` Wayne Scott
2004-09-13 15:21 ` Michael Weissenbacher
2004-09-13 16:13 ` Alex Zarochentsev
2004-09-13 18:52 ` Joe Orton
2004-09-13 19:44 ` Nikita Danilov
2004-09-15 10:55 ` evilninja
2004-09-15 11:41 ` Nikita Danilov
2004-09-16 0:00 ` evilninja
2004-09-13 20:58 ` Alex Zarochentsev [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-15 13:18 Paul Wagland
2004-09-15 14:04 ` Hans Reiser
2004-09-15 14:16 ` Paul Wagland
2004-09-15 15:12 ` Nikita Danilov
2004-09-15 14:45 ` Nikita Danilov
2004-09-15 16:15 ` daniel.poelzleithner
2004-09-15 22:40 ` Hans Reiser
2004-09-16 19:55 ` Toby Dickenson
[not found] ` <2f9ccaae04091615395cfd0730@mail.gmail.com>
2004-09-16 22:40 ` Perry Kundert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040913205812.GD2252@backtop.namesys.com \
--to=zam@namesys.com \
--cc=jorton@redhat.com \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.