| To: | David Chinner <dgc@xxxxxxx> |
|---|---|
| Subject: | [xfs-masters] Re: [PATCH 5 of 11] XFS: Use SEEK_{SET, CUR, END} instead of hardcoded values |
| From: | David Howells <dhowells@xxxxxxxxxx> |
| Date: | Mon, 18 Sep 2006 11:30:35 +0100 |
| Cc: | "Josef 'Jeff' Sipek" <jeffpc@xxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs-masters@xxxxxxxxxxx, akpm@xxxxxxxx, dhowells@xxxxxxxxxx |
| In-reply-to: | <20060918033431.GV3034@xxxxxxxxxxxxxxxxx> |
| References: | <20060918033431.GV3034@xxxxxxxxxxxxxxxxx> <patchbomb.1158455366@xxxxxxxxxxxxxxxxxxxxx> <4cdee5980dad9980ec8f.1158455371@xxxxxxxxxxxxxxxxxxxxx> |
| Reply-to: | xfs-masters@xxxxxxxxxxx |
| Sender: | xfs-masters-bounce@xxxxxxxxxxx |
David Chinner <dgc@xxxxxxx> wrote:
> The hard coded values used in xfs_change_file_space() are documented as part
> of the API to the userspace functions that use this interface in xfsctl(3).
Hmmm... that's a good point. I think you're right on this account, and so the
comments in:
case 0: /*SEEK_SET*/
break;
case 1: /*SEEK_CUR*/
bf->l_start += offset;
break;
case 2: /*SEEK_END*/
bf->l_start += ip->i_d.di_size;
break;
should be stripped off as they are not exactly correct.
David
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [xfs-masters] Re: [PATCH 5 of 11] XFS: Use SEEK_{SET, CUR, END} instead of hardcoded values, David Chinner |
|---|---|
| Next by Date: | [xfs-masters] [Bug 720] New: xfs_da_do_buf error under load on Core 5 current kernel - XFS over LVM on 3Ware 9500 HW RAID, bugzilla-daemon |
| Previous by Thread: | [xfs-masters] Re: [PATCH 5 of 11] XFS: Use SEEK_{SET, CUR, END} instead of hardcoded values, David Chinner |
| Next by Thread: | [xfs-masters] Re: [PATCH 5 of 11] XFS: Use SEEK_{SET, CUR, END} instead of hardcoded values, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |