Messages in this thread | | | Date | Wed, 11 Aug 2004 18:14:30 -0300 | From | Marcelo Tosatti <> | Subject | Re: FW: Linux kernel file offset pointer races |
| |
On Wed, Aug 11, 2004 at 06:26:02PM +0400, Andrey Savochkin wrote: > BTW, f_pos assignments are non-atomic on IA-32 since it's a 64-bit value. > The file position is protected by the BKL in llseek(), but I do not see any > serialization neither in sys_read() nor in generic_file_read() and other > methods. > > Have we accepted that the file position may be corrupted after crossing 2^32 > boundary by 2 processes reading in parallel from the same file? > Or am I missing something?
Yes, as far as I know, parallel users of the same file descriptions (which can race on 64-bit architectures) is expected, we dont care about handling it.
Behaviour is undefined.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |