login
Header Space

 
 

Mailing list archives

Search results

Found 53 matching messages (0.173 seconds). Page 1 of 3.

Re: file offset corruption on 32-bit machines?

... > 64-bit file offset implementation and concludes that on 32-bit > > > machines, Linux ... sync and this could cause rare file offset corruption. > > > http://jeffr-tech.livejournal.com/ ... impossible) to trigger with a sane file usage pattern. Note that you > ...

linux-fsdevel - Jan Kara - Apr 10 2008 - 10:27

Re: file offset corruption on 32-bit machines?

... > 64-bit file offset implementation and concludes that on 32-bit > > > > machines, Linux ... and this could cause rare file offset corruption. > > > > http://jeffr-tech.livejournal.com/ ... impossible) to trigger with a sane file usage pattern. Note that you > ...

linux-fsdevel - Pavel Machek - Apr 11 2008 - 15:26

Re: file offset corruption on 32-bit machines?

... > 64-bit file offset implementation and concludes that on 32-bit > > > > > machines, Linux ... sync and this could cause rare file offset corruption. > > > > > http://jeffr-tech.livejournal.com/ ... it limits max size of file you're able to create. And write/ ...

linux-fsdevel - Jan Kara - Apr 14 2008 - 12:25

Re: file offset corruption on 32-bit machines?

... > 64-bit file offset implementation and concludes that on 32-bit > machines, Linux ... sync and this could cause rare file offset corruption. > > http://jeffr-tech.livejournal.com/ ... is better to live with tiny-race-on-broken-patterns rather than paying for ...

linux-fsdevel - Michal Hocko - Apr 10 2008 - 09:55

Re: file offset corruption on 32-bit machines?

... > 64-bit file offset implementation and concludes that on 32-bit > > machines, Linux ... sync and this could cause rare file offset corruption. > > http://jeffr-tech.livejournal.com/ ... impossible) to trigger with a sane file usage pattern. Note that you > ...

linux-fsdevel - Jiri Kosina - Apr 10 2008 - 10:01

Re: file offset corruption on 32-bit machines?

... > 64-bit file offset implementation and concludes that on 32-bit > > > machines, Linux ... and this could cause rare file offset corruption. > > > http://jeffr-tech.livejournal.com/ ... .txt This is different race with file position IMO. If I understand the ...

linux-fsdevel - Michal Hocko - Apr 10 2008 - 10:31

Re: file offset corruption on 32-bit machines?

... @suse.cz> writes: > [Adding fsdevel list] > > On Tuesday 08 April 2008 10:05: ... 64-bit file offset implementation and concludes that on 32-bit >> machines, Linux ... and this could cause rare file offset corruption. >> >> http://jeffr-tech.livejournal.com ...

linux-fsdevel - Andi Kleen - Apr 10 2008 - 11:33

Re: file offset corruption on 32-bit machines?

... lower > > > > and upper 32-bits of f_pos on CPU1). And the ... is that f_pos > > > > has 32-bits from one file pointer and ... usually don't check that > file position is growing after each ... bug somewhere). But since possible corruptions are quite limited, I don ...

linux-fsdevel - Jan Kara - Apr 10 2008 - 11:56

Re: file offset corruption on 32-bit machines?

... It does not say "repositions the offset to the random number" nor > ... > to hit). Will only work on multicores, but... If lseek not being ... differ in the upper 32 bits of the file position. > I'm not ... is not atomic for 64bit file offsets, so if you happen ...

linux-fsdevel - Lennart Sorensen - Apr 15 2008 - 15:49

Re: file offset corruption on 32-bit machines?

... () function repositions the offset of the open file > associated with > the file descriptor fildes to the argument offset according to >the directive > whence as ... top bits > the same. I would hope anyone doing multithreaded work on a ...

linux-fsdevel - Pavel Machek - Apr 15 2008 - 15:12

Re: file offset corruption on 32-bit machines?

... wide (stores to f_pos from CPU2 must come between the store of lower and > upper 32-bits of f_pos on CPU1). And the only result is that f_pos has > 32-bits from one file pointer and 32-bits from the other one. So ...

linux-fsdevel - Jiri Kosina - Apr 10 2008 - 10:31

Re: file offset corruption on 32-bit machines?

... (stores to f_pos from CPU2 must come between the store of lower and > > upper 32-bits of f_pos on CPU1). And the only result is that f_pos has > > 32-bits from one file pointer and 32-bits from the other one. So ...

linux-fsdevel - Jan Kara - Apr 10 2008 - 11:19

Re: file offset corruption on 32-bit machines?

... (stores to f_pos from CPU2 must come between the store of lower and > > > upper 32-bits of f_pos on CPU1). And the only result is that f_pos has > > > 32-bits from one file pointer and 32-bits from the other one. So ...

linux-fsdevel - Jan Kara - Apr 10 2008 - 11:22

Re: file offset corruption on 32-bit machines?

... lower > > > and upper 32-bits of f_pos on CPU1). And the ... is that f_pos > > > has 32-bits from one file pointer and ... only for end of the file). But do agree, I still ... work with such a big files). > > Honza Best regards -- Michal Hocko ...

linux-fsdevel - Michal Hocko - Apr 10 2008 - 11:37

Re: file offset corruption on 32-bit machines?

... > A:b. Concievably, checks for the file position could be bypassed because of > ... to specify that offset. pread is banned on proc files implemented via seq_files. And ... are MAX_NON_LFS checks which fits into 32 bits. -- To unsubscribe from this list: ...

linux-fsdevel - Alexey Dobriyan - Apr 14 2008 - 14:34

Re: file offset corruption on 32-bit machines?

... any of them. Just focus on the layer in question. The ... some other user of the file. It does that by ensuring ... application. He sees the file getting corrupted and immediately thinks, "what ... But he notices that the corruption isn't consistent with that ...

linux-fsdevel - Bryan Henderson - Apr 15 2008 - 18:11

Re: file offset corruption on 32-bit machines?

... > separate users ever access the file at the same time. > > I'd ... in his application. He sees the file getting corrupted and > immediately thinks, "what if ... hardly justifiable kernel behaviour. Strace / GDB on the application shows a trace which ...

linux-fsdevel - Jamie Lokier - Apr 16 2008 - 05:40

Re: file offset corruption on 32-bit machines?

... must come between the store of lower and > > upper 32-bits of f_pos on CPU1). And the only result is that f_pos has > > 32-bits from one file pointer and 32-bits ... "Bill, look, we understand that you're interested in selling us this operating ...

linux-fsdevel - Matthew Wilcox - Apr 10 2008 - 10:48

Re: file offset corruption on 32-bit machines?

... For example > you can have a file of records of a fixed size ... a pointer to that? SUSv3 says: On files that support seeking (for example, a regular file), the read() shall start at a ... associated with fildes. The file offset shall be incremented by the ...

linux-fsdevel - Jan Kara - Apr 10 2008 - 11:12

Re: file offset corruption on 32-bit machines?

On Thu, Apr 10, 2008 at 04:14:06PM +0100, Jamie Lokier wrote ... equivalents)? pread/pwrite specify an explicit offset and do not change the file offset, so there's no way they ... "Bill, look, we understand that you're interested in selling us this operating ...

linux-fsdevel - Matthew Wilcox - Apr 10 2008 - 11:21

speck-geostationary