Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*extended\s+attributes\s+interface\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*extended\s+attributes\s+interface\s*$/: 15 ]

Total 15 documents matching your query.

1. flush with 2.4.1[4|7]-xfs (score: 1): Author: xxxxxxxxxxxx>; Date: Wed, 30 Jan 2002 14:46:47 -0800 (PST); All the values that go through these syscalls seem to be opaque and filesystem specific. Therefore can I ask the filesystems that use these things use fixed sized types such as "u32" "u16" et al. ins; /archives/xfs/2002-01/msg00880.html (7,563 bytes)
2. hould an xfs_freeze take? (score: 1): Author: xxxxxxxxxxxx>; Date: Thu, 31 Jan 2002 10:10:55 +1100; Absolutely agree. Hopefully not for ia64. The ia32 compatibility mode syscall table is a subset of the i386 table, in particular new syscalls and Linux specific ones tend not to be in arch/ia64/ia32.; /archives/xfs/2002-01/msg00883.html (8,717 bytes)
3. nded attributes interface (score: 1): Author: kaos@xxxxxxx>; Date: Wed, 30 Jan 2002 15:12:17 -0800 (PST); Read this as: forever. Because we have several years worth of users with 32-bit userland distributions on at least sparc64. These people (including me, I have to test it :-) are not going away any ti; /archives/xfs/2002-01/msg00884.html (7,894 bytes)
4. hould an xfs_freeze take? (score: 1): Author: lord@xxxxxxx>; Date: Thu, 31 Jan 2002 10:17:23 +1100; Yes, agreed. The main consumer of this interface currently is Andreas' POSIX ACL code, and IIRC he does use fixed size types for his ACL attributes. The man pages do refer to this issue, I will flesh; /archives/xfs/2002-01/msg00886.html (8,777 bytes)
5. ore (score: 1): Author: deen@xxxxxxx>; Date: Thu, 31 Jan 2002 17:14:15 +0100; The x86-64 project will maintain/extend it "forever" at least if nobody else will do. -Andi; /archives/xfs/2002-01/msg00897.html (8,398 bytes)
6. in bdflush with 2.4.1[4|7]-xfs (score: 1): Author: ck <poznick@xxxxxxxxxxxxxx>; Date: Wed, 30 Jan 2002 14:46:47 -0800 (PST); All the values that go through these syscalls seem to be opaque and filesystem specific. Therefore can I ask the filesystems that use these things use fixed sized types such as "u32" "u16" et al. ins; /archives/xfs/2002-01/msg01809.html (7,563 bytes)
7. in bdflush with 2.4.1[4|7]-xfs (score: 1): Author: " <c.pascoe@xxxxxxxxxxxxxx>; Date: Thu, 31 Jan 2002 10:10:55 +1100; Absolutely agree. Hopefully not for ia64. The ia32 compatibility mode syscall table is a subset of the i386 table, in particular new syscalls and Linux specific ones tend not to be in arch/ia64/ia32.; /archives/xfs/2002-01/msg01812.html (8,717 bytes)
8. : How long should an xfs_freeze take? (score: 1): Author:; Date: Wed, 30 Jan 2002 15:12:17 -0800 (PST); Read this as: forever. Because we have several years worth of users with 32-bit userland distributions on at least sparc64. These people (including me, I have to test it :-) are not going away any ti; /archives/xfs/2002-01/msg01813.html (7,894 bytes)
9. : extended attributes interface (score: 1): Author: >; Date: Thu, 31 Jan 2002 10:17:23 +1100; Yes, agreed. The main consumer of this interface currently is Andreas' POSIX ACL code, and IIRC he does use fixed size types for his ACL attributes. The man pages do refer to this issue, I will flesh; /archives/xfs/2002-01/msg01815.html (8,777 bytes)
10. TAKE - xfs memory allocation, use GFP_KERNEL more (score: 1): Author: c Sandeen <sandeen@xxxxxxx>; Date: Thu, 31 Jan 2002 17:14:15 +0100; The x86-64 project will maintain/extend it "forever" at least if nobody else will do. -Andi; /archives/xfs/2002-01/msg01826.html (8,398 bytes)
11. extended attributes interface (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxx>; Date: Wed, 30 Jan 2002 14:46:47 -0800 (PST); All the values that go through these syscalls seem to be opaque and filesystem specific. Therefore can I ask the filesystems that use these things use fixed sized types such as "u32" "u16" et al. ins; /archives/xfs/2002-01/msg02738.html (7,563 bytes)
12. Re: extended attributes interface (score: 1): Author: Keith Owens <kaos@xxxxxxx>; Date: Thu, 31 Jan 2002 10:10:55 +1100; Absolutely agree. Hopefully not for ia64. The ia32 compatibility mode syscall table is a subset of the i386 table, in particular new syscalls and Linux specific ones tend not to be in arch/ia64/ia32.; /archives/xfs/2002-01/msg02741.html (8,754 bytes)
13. Re: extended attributes interface (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxx>; Date: Wed, 30 Jan 2002 15:12:17 -0800 (PST); Read this as: forever. Because we have several years worth of users with 32-bit userland distributions on at least sparc64. These people (including me, I have to test it :-) are not going away any ti; /archives/xfs/2002-01/msg02742.html (7,977 bytes)
14. Re: extended attributes interface (score: 1): Author: Nathan Scott <nathans@xxxxxxx>; Date: Thu, 31 Jan 2002 10:17:23 +1100; Yes, agreed. The main consumer of this interface currently is Andreas' POSIX ACL code, and IIRC he does use fixed size types for his ACL attributes. The man pages do refer to this issue, I will flesh; /archives/xfs/2002-01/msg02744.html (8,894 bytes)
15. Re: extended attributes interface (score: 1): Author: Andi Kleen <ak@xxxxxxx>; Date: Thu, 31 Jan 2002 17:14:15 +0100; The x86-64 project will maintain/extend it "forever" at least if nobody else will do. -Andi; /archives/xfs/2002-01/msg02755.html (8,537 bytes)

Current List: 1 - 15
Page: [1]