|
Re: write operation returns incorrect value in case device is out of space: msg#00080linux.file-systems.yaffs
On 12/22/05, Todd Poynor <tpoynor@xxxxxxxxxx> wrote:
Mikhail Ryleev wrote: For example it is called by generic_file_write routine which is an implementation of "write" call.
Since it is that generic, we have to be extremely careful what we return here.
As for partial count return, if we change the state of the file, advance file pointer or change the size of the file,
we have to let the caller know that that happened. An alternative would be to completely discard changes,
probably it is much better but far more complex.
> 2. device is out of space while creating new object. In this case ENOMEM is returned by yaffs_mknod call in case it failed to create new object for whatever reason and not in that patch.
I do not have simple solution for that, other then replace it with ENOSPC which is arguably not much better.
Is a check for nWritten < 0 (-ENOMEM) appropriate? Or else ( nWritten _______________________________________________ yaffs mailing list yaffs@xxxxxxxxxxxxxxxxxxxxxx http://stoneboat.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: write operation returns incorrect value in case device is out of space: 00080, Todd Poynor |
|---|---|
| Next by Date: | {Spam} Yaffs2 remount problem: 00080, afewgoodman |
| Previous by Thread: | Re: write operation returns incorrect value in case device is out of spacei: 00080, Todd Poynor |
| Next by Thread: | {Spam} Yaffs2 remount problem: 00080, afewgoodman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |