Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*fsetxattr\s+fails\s+on\s+a\s+writable\s+descriptor\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*fsetxattr\s+fails\s+on\s+a\s+writable\s+descriptor\?\s*$/: 6 ]

Total 6 documents matching your query.

1. fsetxattr() fails on a writable descriptor? (score: 1): Author: Pádraig Brady <P@xxxxxxxxxxxxxx>; Date: Tue, 8 Sep 2009 12:29:49 +0100; fsetxattr() is failing for me when the permissions are readonly but the descriptor is writable as demonstrated by the program below. I've tried this on ext3 and ext4 with libattr-2.4.43-3.fc11.i586 a; /archives/xfs/2009-09/msg00096.html (8,895 bytes)
2. Re: fsetxattr() fails on a writable descriptor? (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Tue, 8 Sep 2009 14:40:49 -0400; That's not XFS specifci behaviour. For all xattr operations, fd-based or not we always do the full permission checks, and have done so since day one. Check the routined xattr_permission in fs/xattr.c; /archives/xfs/2009-09/msg00100.html (8,758 bytes)
3. Re: fsetxattr() fails on a writable descriptor? (score: 1): Author: Pádraig Brady <P@xxxxxxxxxxxxxx>; Date: Wed, 09 Sep 2009 22:23:39 +0100; Sorry if you get this twice. Resending using another server... Thanks for this info Christoph. http://lxr.linux.no/#linux+v2.6.30.5/fs/xattr.c The specific issue we have is that `cp --preserve=xattr`; /archives/xfs/2009-09/msg00109.html (10,132 bytes)
4. Re: fsetxattr() fails on a writable descriptor? (score: 1): Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>; Date: Thu, 10 Sep 2009 00:14:10 +0200; In that context I would call it a bug - shouldn't it be fixed? When you copy and want xattrs, and it fails sometimes, that's not what's expected. So if xattr is broken from day one and it should stay; /archives/xfs/2009-09/msg00110.html (9,315 bytes)
5. Re: fsetxattr() fails on a writable descriptor? (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Tue, 13 Oct 2009 19:58:05 -0400; It seems pretty late for change behaviour that has been around since 2002. But if this was a new interface I would agree with you that the behaviour is illogical.; /archives/xfs/2009-10/msg00133.html (8,223 bytes)
6. Re: fsetxattr() fails on a writable descriptor? (score: 1): Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>; Date: Wed, 14 Oct 2009 03:17:09 +0200; I didn't restrict to fix xattr behaviour, but "cp" should be fixed. After all, the bug exists since 2002, so "cp" should also work around it to get it's own parameters right. mfg zmi -- // Michael Mo; /archives/xfs/2009-10/msg00137.html (9,022 bytes)

Current List: 1 - 6
Page: [1]