| To: | slord@xxxxxxx |
|---|---|
| Subject: | Re: TAKE - XFS/Linux Extended Attributes. |
| From: | "Andi Kleen" <ak@xxxxxxx> |
| Date: | Fri, 28 Jul 2000 00:39:22 +0200 |
| Cc: | "Andi Kleen" <ak@xxxxxxx>, Ted Kline <jtk@xxxxxxx>, linux-xfs@xxxxxxxxxxx, casey@xxxxxxxxxxxx |
| In-reply-to: | <200007271919.OAA30531@xxxxxxxxxxxxxxxxxxxx>; from unknown@xxxxxxx on Thu, Jul 27, 2000 at 02:19:25PM -0500 |
| References: | <ak@xxxxxxx> <200007271919.OAA30531@xxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
On Thu, Jul 27, 2000 at 02:19:25PM -0500, The Unknown User-ID wrote: > > I agree - except there is no 'approved' interface for extended attributes > yet. This is as much a way for us to exercise the code in the kernel and a > proof of concept as anything else. If the final version of an extended > attribute interface is different then we will change to match it. The problem is not really the interface, just the syscall slot number. I doubt it will be a problem to get a sysxfs() reserved, you could hook the interface onto that and still switch over to the official interface later. Just privately reserving syscall numbers causes problems, because they could be reused by someone else and break compatibility, causing more pain than needed. BTW, it is nice that you start to implement code for that. -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | TAKE - Fix error return on bad "fd" for attr interface., Ted Kline |
|---|---|
| Next by Date: | TAKE - fix xfs_db type attr breakage x 2, Daniel Moore |
| Previous by Thread: | Re: TAKE - XFS/Linux Extended Attributes., 858 |
| Next by Thread: | Re: TAKE - XFS/Linux Extended Attributes., Curtis Anderson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |