Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+2\/3\]\s+simplify\s+xfs

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+2\/3\]\s+simplify\s+xfs_setattr\s*$/: 24 ]

Total 24 documents matching your query.

1. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author: Christoph Hellwig <hch@xxxxxx>; Date: Sat, 5 Jul 2008 19:20:21 +0200; As per discussion with Tim here's a version that doesn't require the generic ACL patch applied before: Signed-off-by: Christoph Hellwig <hch@xxxxxx> Index: linux-2.6-xfs/fs/xfs/dmapi/xfs_dm.c == -- l; /archives/xfs/2008-07/msg00063.html (45,842 bytes)
2. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author: Timothy Shimmin <tes@xxxxxxx>; Date: Wed, 09 Jul 2008 18:58:21 +1000; Looks reasonable to me :) (odd notes below) --Tim o stop using bhv_vattr_t and move over to struct iattr. where va_mask -> ia_valid Looks good. So just need to keep the changes to the inode, don't ne; /archives/xfs/2008-07/msg00134.html (57,408 bytes)
3. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author:; Date: Wed, 9 Jul 2008 18:29:14 +0200; Yeah, not that ATTR_NO_BLOCK doesn't actually exist in any tree I have access to, and thus it's not actually handled in the new xfs_setattr. Probably. Note that linux uses the ATTR_ flags only for ->; /archives/xfs/2008-07/msg00146.html (10,005 bytes)
4. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author:; Date: Fri, 11 Jul 2008 10:32:57 +1000; Hmm...confusing re NO_BLOCK. 1 linux-2.6/xfs_vnode.h <global> 228 #define ATTR_NONBLOCK 0x100 2 linux-2.6/xfs_ioctl.c xfs_ioc_space 686 attr_flags |= ATTR_NONBLOCK; 3 linux-2.6/xfs_ioctl.c xfs_ioc_fs; /archives/xfs/2008-07/msg00166.html (11,626 bytes)
5. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author:; Date: Fri, 11 Jul 2008 11:07:59 +1000; Look in SLES9 and SLES10. It's used to enable the NFS server to return EAGAIN for truncates that might block for a long time. This can occur if a file migration to/from HSM is in progress. This will; /archives/xfs/2008-07/msg00167.html (10,312 bytes)
6. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author:; Date: Fri, 11 Jul 2008 03:10:17 +0200; We scan till set XFS_ATTR_NONBLOCK, just not coming from xfs_vn_setattr. Currently that's only done in xfs_ioc_space. --end quoted text--; /archives/xfs/2008-07/msg00168.html (11,402 bytes)
7. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author:; Date: Fri, 11 Jul 2008 03:11:14 +0200; Get proper hsm support in mainline and we can talk about enhancing subsystems to deal with it.; /archives/xfs/2008-07/msg00169.html (8,459 bytes)
8. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author: xxxxx>; Date: Sat, 5 Jul 2008 19:20:21 +0200; As per discussion with Tim here's a version that doesn't require the generic ACL patch applied before: Signed-off-by: Christoph Hellwig <hch@xxxxxx> Index: linux-2.6-xfs/fs/xfs/dmapi/xfs_dm.c == -- l; /archives/xfs/2008-07/msg00686.html (45,842 bytes)
9. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author: xxxxx>; Date: Wed, 09 Jul 2008 18:58:21 +1000; Looks reasonable to me :) (odd notes below) --Tim o stop using bhv_vattr_t and move over to struct iattr. where va_mask -> ia_valid Looks good. So just need to keep the changes to the inode, don't ne; /archives/xfs/2008-07/msg00757.html (57,408 bytes)
10. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author: xxxxxx>; Date: Wed, 9 Jul 2008 18:29:14 +0200; Yeah, not that ATTR_NO_BLOCK doesn't actually exist in any tree I have access to, and thus it's not actually handled in the new xfs_setattr. Probably. Note that linux uses the ATTR_ flags only for ->; /archives/xfs/2008-07/msg00769.html (10,005 bytes)
11. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author: xxxxxx>; Date: Fri, 11 Jul 2008 10:32:57 +1000; Hmm...confusing re NO_BLOCK. 1 linux-2.6/xfs_vnode.h <global> 228 #define ATTR_NONBLOCK 0x100 2 linux-2.6/xfs_ioctl.c xfs_ioc_space 686 attr_flags |= ATTR_NONBLOCK; 3 linux-2.6/xfs_ioctl.c xfs_ioc_fs; /archives/xfs/2008-07/msg00789.html (11,626 bytes)
12. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author: xxxxxx>; Date: Fri, 11 Jul 2008 11:07:59 +1000; Look in SLES9 and SLES10. It's used to enable the NFS server to return EAGAIN for truncates that might block for a long time. This can occur if a file migration to/from HSM is in progress. This will; /archives/xfs/2008-07/msg00790.html (10,312 bytes)
13. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author: xxxxxx>; Date: Fri, 11 Jul 2008 03:10:17 +0200; We scan till set XFS_ATTR_NONBLOCK, just not coming from xfs_vn_setattr. Currently that's only done in xfs_ioc_space. --end quoted text--; /archives/xfs/2008-07/msg00791.html (11,402 bytes)
14. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author: xxxxxx>; Date: Fri, 11 Jul 2008 03:11:14 +0200; Get proper hsm support in mainline and we can talk about enhancing subsystems to deal with it.; /archives/xfs/2008-07/msg00792.html (8,459 bytes)
15. [PATCH 2/3] simplify xfs_setattr (score: 1): Author: Christoph Hellwig <hch@xxxxxx>; Date: Fri, 27 Jun 2008 17:45:57 +0200; Now that xfs_setattr is only used for attributes set from ->setattr it can be switched to take struct iattr directly and thus simplify the implementation greatly. Also rename the ATTR_ flags to XFS_A; /archives/xfs/2008-06/msg00421.html (43,116 bytes)
16. [PATCH 2/3] simplify xfs_setattr (score: 1): Author: Christoph Hellwig <hch@xxxxxx>; Date: Fri, 27 Jun 2008 17:45:57 +0200; Now that xfs_setattr is only used for attributes set from ->setattr it can be switched to take struct iattr directly and thus simplify the implementation greatly. Also rename the ATTR_ flags to XFS_A; /archives/xfs/2008-06/msg00881.html (43,116 bytes)
17. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author: Christoph Hellwig <hch@xxxxxx>; Date: Sat, 5 Jul 2008 19:20:21 +0200; As per discussion with Tim here's a version that doesn't require the generic ACL patch applied before: Signed-off-by: Christoph Hellwig <hch@xxxxxx> Index: linux-2.6-xfs/fs/xfs/dmapi/xfs_dm.c == -- l; /archives/xfs/2008-07/msg01309.html (45,958 bytes)
18. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author: Timothy Shimmin <tes@xxxxxxx>; Date: Wed, 09 Jul 2008 18:58:21 +1000; Looks reasonable to me :) (odd notes below) --Tim o stop using bhv_vattr_t and move over to struct iattr. where va_mask -> ia_valid Looks good. So just need to keep the changes to the inode, don't ne; /archives/xfs/2008-07/msg01380.html (57,524 bytes)
19. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author: Christoph Hellwig <hch@xxxxxx>; Date: Wed, 9 Jul 2008 18:29:14 +0200; Yeah, not that ATTR_NO_BLOCK doesn't actually exist in any tree I have access to, and thus it's not actually handled in the new xfs_setattr. Probably. Note that linux uses the ATTR_ flags only for ->; /archives/xfs/2008-07/msg01392.html (10,140 bytes)
20. Re: [PATCH 2/3] simplify xfs_setattr (score: 1): Author: Timothy Shimmin <tes@xxxxxxx>; Date: Fri, 11 Jul 2008 10:32:57 +1000; Hmm...confusing re NO_BLOCK. 1 linux-2.6/xfs_vnode.h <global> 228 #define ATTR_NONBLOCK 0x100 2 linux-2.6/xfs_ioctl.c xfs_ioc_space 686 attr_flags |= ATTR_NONBLOCK; 3 linux-2.6/xfs_ioctl.c xfs_ioc_fs; /archives/xfs/2008-07/msg01412.html (11,797 bytes)

Current List: 1 - 20
Page: [1] [2]