From: Fredrik Tolf <fredrik@dolda2000.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Fredrik Tolf <fredrik@dolda2000.com>, reiserfs-list@namesys.com
Subject: Re: XATTR bugs
Date: Wed, 10 Dec 2003 02:22:20 +0100 [thread overview]
Message-ID: <16342.30028.148943.409122@pc7.dolda2000.com> (raw)
In-Reply-To: <3FD65B57.8040603@suse.com>
Jeff Mahoney writes:
> | The first bug was in inode.c and was really simple. The only thing was
> | that #include <linux/quotaops.h> was missing. It is necessary for
> | DQUOT_TRANSFER, which is used by the xattr patch, and as such the
> | module won't load.
>
> This bug was fixed in the updated patches.
>
> | The second one was a bit more subtle. I'm using this ReiserFS to serve
> | NFS, and I discovered that there was an ACL-related bug in
> | reiserfs_setattr (also from inode.c). In the end of that function
> | (line 2464 in my kernel), it makes a call to reiserfs_acl_chmod, like
> | this:
> [...]
> | The thing is that I don't know ReiserFS, and so I don't really know
> | what I'm doing. If you think this breaks anything, please tell me
> | so. In any other case, I guess it would be a good thing to change the
> | patches into this.
>
> This bug, however, I don't believe is a bug in my code. This code works
> fine on 2.4 kernels, and after a few minutes of searching, I've found
> the difference.
[...]
>
> The problem needs to be addressed there, not in the ReiserFS code. I'll
> check out when and why that bit of code became errnoneous in the 2.6
> kernel later this evening; I'm headed out the door at the moment.
These are not the greatest problems with the XATTR patches,
though; they were only what I discovered initially. The greatest
problem (I don't know if this might not appear on 2.4 kernels, but it
certainly did occur on all my 2.6 kernels) is that ACLs can suddenly
"disappear".
I don't know exactly what it was that happened, but sometimes (without
any pattern that I could notice), the ACLs would simply become
ineffective. The XATTR for the ACLs was still there, but it was as if
it wasn't taken into account for any kind of operation. When checking
with getfattr, the ACL attribute was still there and looked just as it
did before whatever happened happened, but in every other aspect it
was as if it wasn't there anymore. The only way to solve it was to run
"setfacl -b" on the affected file and then recreate the ACL.
In fact, this forced me to abandon ReiserFS in favor of XFS.
Regrettable as it may be, I didn't want to live without ACLs, and I
had too much on my hands to start debugging it... :-(
Fredrik Tolf
next prev parent reply other threads:[~2003-12-10 1:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 0:27 XATTR bugs Fredrik Tolf
2003-11-25 14:05 ` Hans Reiser
2003-11-26 2:13 ` Fredrik Tolf
2003-12-09 23:31 ` Jeff Mahoney
2003-12-10 1:22 ` Fredrik Tolf [this message]
2003-12-10 2:10 ` Jeff Mahoney
2003-12-10 2:27 ` Fredrik Tolf
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=16342.30028.148943.409122@pc7.dolda2000.com \
--to=fredrik@dolda2000.com \
--cc=jeffm@suse.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.