Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[UPDATED\s+RFC\]\s+Create\s+with\s+EA\s+initial\s+work\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[UPDATED\s+RFC\]\s+Create\s+with\s+EA\s+initial\s+work\s*$/: 12 ]

Total 12 documents matching your query.

1. [UPDATED RFC] Create with EA initial work (score: 1): Author:; Date: Thu, 10 Jul 2008 17:39:01 +1000; Thanks to everyone for the review of the former patchset, this ones fixes the bugs found by dgc, changes the naming of the *_trans_* functions, splits out xfs_bmap_add_attrfork{,_trans} to have one v; /archives/xfs/2008-07/msg00161.html (8,935 bytes)
2. Re: [UPDATED RFC] Create with EA initial work (score: 1): Author:; Date: Tue, 22 Jul 2008 00:38:51 -0400; There are multiple ways to deal with inodes linked to transactions. In all cases it needs to be linked into the transaction by xfs_trans_ijoin, or the opencoded equivalent for a new inode in xfs_tran; /archives/xfs/2008-07/msg00331.html (10,191 bytes)
3. Re: [UPDATED RFC] Create with EA initial work (score: 1): Author:; Date: Wed, 23 Jul 2008 15:35:23 +1000; Shouldn't the inode already be in the transaction ? we just created it and added it to the directory ? xfs_create() xfs_dir_ialloc(tp, dp, ip) xfs_ialloc(tp, dp, ip) xfs_trans_iget(tp, ip) and it has; /archives/xfs/2008-07/msg00375.html (11,347 bytes)
4. Re: [UPDATED RFC] Create with EA initial work (score: 1): Author:; Date: Wed, 23 Jul 2008 03:51:45 -0400; Yes, it is in the transaction. I just meant to say xfs_trans_iget opencodes the transaction linking otherwise done in xfs_trans_ijoin. I'm not sure. What we need to is to make sure we don't have mult; /archives/xfs/2008-07/msg00391.html (12,947 bytes)
5. [UPDATED RFC] Create with EA initial work (score: 1): Author: xxxxxx>; Date: Thu, 10 Jul 2008 17:39:01 +1000; Thanks to everyone for the review of the former patchset, this ones fixes the bugs found by dgc, changes the naming of the *_trans_* functions, splits out xfs_bmap_add_attrfork{,_trans} to have one v; /archives/xfs/2008-07/msg00784.html (8,935 bytes)
6. Re: [UPDATED RFC] Create with EA initial work (score: 1): Author: xxxxxx>; Date: Tue, 22 Jul 2008 00:38:51 -0400; There are multiple ways to deal with inodes linked to transactions. In all cases it needs to be linked into the transaction by xfs_trans_ijoin, or the opencoded equivalent for a new inode in xfs_tran; /archives/xfs/2008-07/msg00954.html (10,191 bytes)
7. Re: [UPDATED RFC] Create with EA initial work (score: 1): Author: xxxxxx>; Date: Wed, 23 Jul 2008 15:35:23 +1000; Shouldn't the inode already be in the transaction ? we just created it and added it to the directory ? xfs_create() xfs_dir_ialloc(tp, dp, ip) xfs_ialloc(tp, dp, ip) xfs_trans_iget(tp, ip) and it has; /archives/xfs/2008-07/msg00998.html (11,347 bytes)
8. Re: [UPDATED RFC] Create with EA initial work (score: 1): Author: xxxxxx>; Date: Wed, 23 Jul 2008 03:51:45 -0400; Yes, it is in the transaction. I just meant to say xfs_trans_iget opencodes the transaction linking otherwise done in xfs_trans_ijoin. I'm not sure. What we need to is to make sure we don't have mult; /archives/xfs/2008-07/msg01014.html (12,947 bytes)
9. [UPDATED RFC] Create with EA initial work (score: 1): Author: Niv Sardi <xaiki@xxxxxxx>; Date: Thu, 10 Jul 2008 17:39:01 +1000; Thanks to everyone for the review of the former patchset, this ones fixes the bugs found by dgc, changes the naming of the *_trans_* functions, splits out xfs_bmap_add_attrfork{,_trans} to have one v; /archives/xfs/2008-07/msg01407.html (9,085 bytes)
10. Re: [UPDATED RFC] Create with EA initial work (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Tue, 22 Jul 2008 00:38:51 -0400; There are multiple ways to deal with inodes linked to transactions. In all cases it needs to be linked into the transaction by xfs_trans_ijoin, or the opencoded equivalent for a new inode in xfs_tran; /archives/xfs/2008-07/msg01577.html (10,357 bytes)
11. Re: [UPDATED RFC] Create with EA initial work (score: 1): Author: Niv Sardi <xaiki@xxxxxxx>; Date: Wed, 23 Jul 2008 15:35:23 +1000; Shouldn't the inode already be in the transaction ? we just created it and added it to the directory ? xfs_create() xfs_dir_ialloc(tp, dp, ip) xfs_ialloc(tp, dp, ip) xfs_trans_iget(tp, ip) and it has; /archives/xfs/2008-07/msg01621.html (11,525 bytes)
12. Re: [UPDATED RFC] Create with EA initial work (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 23 Jul 2008 03:51:45 -0400; Yes, it is in the transaction. I just meant to say xfs_trans_iget opencodes the transaction linking otherwise done in xfs_trans_ijoin. I'm not sure. What we need to is to make sure we don't have mult; /archives/xfs/2008-07/msg01637.html (13,140 bytes)

Current List: 1 - 12
Page: [1]