* XATTR support
@ 2004-07-29 1:08 Steve French
2004-07-29 7:35 ` Hans Reiser
0 siblings, 1 reply; 2+ messages in thread
From: Steve French @ 2004-07-29 1:08 UTC (permalink / raw)
To: linux-kernel
I noticed that ext2, ext3, reiserfs, and jfs mark (in menuconfig) their
xattr support as an optional subfeature which is a little surprising
because the xattr support in those filesystems is no longer
experimental/unstable and there seems little harm in just always
building xattr support in to those filesystems. Now that I have added
xattr support to the cifs filesystem in the cifs development bk tree, I
was planning on making xattr support a suboption (in menuconfig)
following the example of those others, at least at first (the suboption
also would be marked experimental for a while).
Is there any particular reason to always configure xattr support (not
make it a menuconfig option) for individual filesystems?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: XATTR support
2004-07-29 1:08 XATTR support Steve French
@ 2004-07-29 7:35 ` Hans Reiser
0 siblings, 0 replies; 2+ messages in thread
From: Hans Reiser @ 2004-07-29 7:35 UTC (permalink / raw)
To: Steve French; +Cc: linux-kernel
Steve French wrote:
>I noticed that ext2, ext3, reiserfs, and jfs mark (in menuconfig) their
>xattr support as an optional subfeature which is a little surprising
>because the xattr support in those filesystems is no longer
>experimental/unstable
>
well, xattr related bugs were found just a few months ago.... and some
of us think xattrs are a bad idea in principle.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-07-29 7:35 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-07-29 1:08 XATTR support Steve French
2004-07-29 7:35 ` Hans Reiser
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox