From: Jeff Mahoney <jeffm@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Sergey Vlasov <vsu@altlinux.ru>,
Bernd Schubert <bernd-schubert@gmx.de>,
Chris Wright <chrisw@sous-sol.org>,
John M Flinchbaugh <john@hjsoft.com>,
reiserfs-list@namesys.com, Sam Vilain <sam@vilain.net>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.15 Bug? New security model?
Date: Mon, 13 Feb 2006 10:24:42 -0500 [thread overview]
Message-ID: <43F0A4BA.20401@suse.com> (raw)
In-Reply-To: <43F01D70.70600@namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hans Reiser wrote:
> This is an xattr bug, and I'll let jeff answer it.
Hans -
This bug is about inode attributes (the chattr type), not extended
attributes (the setfacl/setfattr type). Regardless, it's the root cause
of the random attributes we were seeing when the REISERFS_ATTRS
enable-by-default problem was corrected. Thanks to some other people on
the list, I was able to post some patches to address it yesterday evening.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFD8KS5LPWxlyuTD7IRApKRAJ0SdbS+/KzO8Kn7RMfVQ2KfwNSg/gCfXIdE
KlxigEBlCZixvy7PObKebE0=
=3wk5
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-02-13 15:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 1:12 2.6.15 Bug? New security model? Bernd Schubert
2006-02-08 1:31 ` Sam Vilain
2006-02-08 5:37 ` John M Flinchbaugh
2006-02-08 12:14 ` Bernd Schubert
2006-02-08 20:50 ` Chris Wright
2006-02-08 21:46 ` Bernd Schubert
2006-02-08 22:11 ` Chris Wright
2006-02-11 21:55 ` Sergey Vlasov
2006-02-11 23:50 ` Bernd Schubert
2006-02-12 18:44 ` Sergey Vlasov
2006-02-12 17:57 ` Jeff Mahoney
2006-02-12 19:21 ` Sergey Vlasov
2006-02-12 23:03 ` Bernd Schubert
2006-02-13 17:52 ` Sergey Vlasov
2006-02-12 23:10 ` Bernd Schubert
2006-02-13 5:47 ` Hans Reiser
2006-02-13 15:24 ` Jeff Mahoney [this message]
2006-02-13 16:39 ` Hans Reiser
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=43F0A4BA.20401@suse.com \
--to=jeffm@suse.com \
--cc=bernd-schubert@gmx.de \
--cc=chrisw@sous-sol.org \
--cc=john@hjsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=sam@vilain.net \
--cc=vsu@altlinux.ru \
/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.