Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+xfsprogs\:\s+check\s+for\s+size\s+parsing\s+errors\s+in\s+xfs_quota\s*$/: 5 ]

Total 5 documents matching your query.

1. [PATCH] xfsprogs: check for size parsing errors in xfs_quota (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxx>
Date: Mon, 23 Jan 2012 11:31:53 -0600
Doing something like will cause cvtnum to fail and return a value of -1LL (because it cannot parse the decimal), but the quota caller doesn't check for this error value, casts it to U64, shifts right
/archives/xfs/2012-01/msg00302.html (8,210 bytes)

2. Re: [PATCH] xfsprogs: check for size parsing errors in xfs_quota (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon, 23 Jan 2012 14:59:22 -0500
Can you add a test case for it, please?
/archives/xfs/2012-01/msg00318.html (7,837 bytes)

3. Re: [PATCH] xfsprogs: check for size parsing errors in xfs_quota (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Mon, 23 Jan 2012 23:07:35 -0600
sure... I have quite a backlog of tests I need to get pushed to git :( Is that an ack for the patch, though? :) -Eric
/archives/xfs/2012-01/msg00329.html (8,565 bytes)

4. Re: [PATCH] xfsprogs: check for size parsing errors in xfs_quota (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 24 Jan 2012 12:56:12 -0500
Why do you replace the shift by nine with a shift by 8? Also please don't introduce new overly long lines, just move the translated string to a line of its own, indented by a single tab similar to h
/archives/xfs/2012-01/msg00360.html (8,653 bytes)

5. Re: [PATCH] xfsprogs: check for size parsing errors in xfs_quota (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxx>
Date: Tue, 24 Jan 2012 11:58:12 -0600
yeargh, NFI - vi gone wild? Ok, sure, sorry. TBH I noticed it but there was such a long line below I didn't worry. Will resend. -Eric
/archives/xfs/2012-01/msg00361.html (9,147 bytes)


This search system is powered by Namazu