Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Review\]\s+Improve\s+XFS\s+error\s+checking\s+and\s+propagation\s*$/: 15 ]

Total 15 documents matching your query.

1. Re: [Review] Improve XFS error checking and propagation (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Wed, 2 Apr 2008 09:00:44 +1000
-- Dave Chinner Principal Engineer SGI Australian Software Group
/archives/xfs/2008-04/msg00013.html (28,407 bytes)

2. Re: [Review] Improve XFS error checking and propagation (score: 1)
Author: Niv Sardi <xaiki@xxxxxxxxxxxxx>
Date: Wed, 02 Apr 2008 13:58:09 +1100
All looks good except some minor typo-editing, and NOK xfs-mustcheck-quotamount.patch # need to check if can happen when forcing quotas I'm not sure what happens if we really DO want quotas (specifie
/archives/xfs/2008-04/msg00016.html (10,081 bytes)

3. Re: [Review] Improve XFS error checking and propagation (score: 1)
Author: Niv Sardi <xaiki@xxxxxxxxxxxxx>
Date: Wed, 02 Apr 2008 15:31:37 +1100
OK, I wasn't sure. All the rest are minor aesthetics/typos my messed up notes, and can be ignoredâ Oops, the edit was for: -+STATIC void /* success (>= minlen) */ ++STATIC void as it didn't really
/archives/xfs/2008-04/msg00019.html (12,513 bytes)

4. Re: [Review] Improve XFS error checking and propagation (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Wed, 2 Apr 2008 15:12:23 +1000
Ok, Fixed. Ok. If it involves splitting a string into 3 lines because of indentation, then I tend to do one long line. i.e. this: if (error) xfs_fs_cmn_err(CE_WARN, mp, "xfs_qm_dquot_logitem_pushbuf:
/archives/xfs/2008-04/msg00021.html (11,686 bytes)

5. inode generation number initialisation (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Wed, 2 Apr 2008 09:00:44 +1000
not accurate - the callback chain is removed in bulk then walked without the lock, but will loop over the iclog chain in case callbacks were added while processing the chain (not sure if that
/archives/xfs/2008-04/msg00609.html (28,407 bytes)

6. () (score: 1)
Author: Niv Sardi <xaiki@xxxxxxxxxxxxx>
Date: Wed, 02 Apr 2008 13:58:09 +1100
, can you repost this patch with a Signed-off-by tag and..... No need for "__" in the tmp var, nor the () around log... Cheers, Dave. -- Dave Chinner Principal Engineer SGI Australian Software
/archives/xfs/2008-04/msg00612.html (10,081 bytes)

7. : [Patch] Per iclog callback chain lock (score: 1)
Author: Niv Sardi <xaiki@xxxxxxxxxxxxx>
Date: Wed, 02 Apr 2008 15:31:37 +1100
# need to check if can happen when forcing quotas I'm not sure what happens if we really DO want quotas (specifie
/archives/xfs/2008-04/msg00615.html (12,513 bytes)

8. : [Patch] Per iclog callback chain lock (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Wed, 2 Apr 2008 15:12:23 +1000
wasn't sure. All the rest are minor aesthetics/typos my messed up notes, and can be ignoredâ Oops, the edit was for: -+STATIC void /* success (>= minlen) */ ++STATIC void as it didn't really
/archives/xfs/2008-04/msg00617.html (11,686 bytes)

9. [Review] Improve XFS error checking and propagation (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Tue, 11 Mar 2008 12:04:21 +1100
A recent paper at the FAST08 conference highlighted a large number of unchecked error paths in Linux filesystems and I/O layers. As a subsystem, XFS had the highest aggregate numbers of bad error pro
/archives/xfs/2008-03/msg00113.html (23,442 bytes)

10. CH, RFC] - remove mounpoint UUID code (score: 1)
Author: xxxxxxxxx>
Date: Tue, 11 Mar 2008 12:04:21 +1100
you'd probably be ok. Doing this to a mounted, rw filesystem is asking for trouble. If the shutdown is occurring after you've run xfs_rep
/archives/xfs/2008-03/msg00502.html (23,442 bytes)

11. Re: [Review] Improve XFS error checking and propagation (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Wed, 2 Apr 2008 09:00:44 +1000
ping? -- Dave Chinner Principal Engineer SGI Australian Software Group
/archives/xfs/2008-04/msg01205.html (28,615 bytes)

12. Re: [Review] Improve XFS error checking and propagation (score: 1)
Author: Niv Sardi <xaiki@xxxxxxxxxxxxx>
Date: Wed, 02 Apr 2008 13:58:09 +1100
All looks good except some minor typo-editing, and NOK xfs-mustcheck-quotamount.patch # need to check if can happen when forcing quotas I'm not sure what happens if we really DO want quotas (specifie
/archives/xfs/2008-04/msg01208.html (10,223 bytes)

13. Re: [Review] Improve XFS error checking and propagation (score: 1)
Author: Niv Sardi <xaiki@xxxxxxxxxxxxx>
Date: Wed, 02 Apr 2008 15:31:37 +1100
OK, I wasn't sure. All the rest are minor aesthetics/typos my messed up notes, and can be ignored Oops, the edit was for: -+STATIC void /* success (>= minlen) */ ++STATIC void as it didn't really mak
/archives/xfs/2008-04/msg01211.html (12,772 bytes)

14. Re: [Review] Improve XFS error checking and propagation (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Wed, 2 Apr 2008 15:12:23 +1000
Ok, Fixed. Ok. If it involves splitting a string into 3 lines because of indentation, then I tend to do one long line. i.e. this: if (error) xfs_fs_cmn_err(CE_WARN, mp, "xfs_qm_dquot_logitem_pushbuf:
/archives/xfs/2008-04/msg01213.html (11,910 bytes)

15. [Review] Improve XFS error checking and propagation (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Tue, 11 Mar 2008 12:04:21 +1100
A recent paper at the FAST08 conference highlighted a large number of unchecked error paths in Linux filesystems and I/O layers. As a subsystem, XFS had the highest aggregate numbers of bad error pro
/archives/xfs/2008-03/msg00891.html (23,532 bytes)


This search system is powered by Namazu