[Bug 17390] New: multiple overlapping reads / writes bigger than SO_SNDBUF / RCV result in data corruption
http://bugs.winehq.org/show_bug.cgi?id=17390
Summary: multiple overlapping reads / writes bigger than SO_SNDBUF / RCV result in data corruption Product: Wine Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: ntdll AssignedTo: wine-bugs@winehq.org ReportedBy: lkcl@lkcl.net
multiple readers of the same filedescriptor, NtReadFile, when reading data amounts that are larger than the SO_RCVBUF and/or SO_SNDBUF, could potentially end up corrupting the data because of overlaps in the reads. solutions involve having to do per-file critical sections and YES that's a generic problem even on standard files not just pipes not just messagemode pipes ALL files.
likewise multiple writers to same filedescriptor, NtWriteFile.
http://bugs.winehq.org/show_bug.cgi?id=17390
--- Comment #1 from Austin English austinenglish@gmail.com 2009-08-26 13:23:27 --- Is this still present in current (1.1.28 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=17390
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |ABANDONED
--- Comment #2 from Austin English austinenglish@gmail.com 2010-09-07 16:59:24 CDT --- No response in over a year, marking abandoned. If this is still an issue in current (1.3.2 or newer) wine, and you can provide the needed information, feel free to reopen.
http://bugs.winehq.org/show_bug.cgi?id=17390
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Austin English austinenglish@gmail.com 2010-09-07 17:12:10 CDT --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=17390
--- Comment #4 from Luke Kenneth Casson Leighton lkcl@lkcl.net 2010-09-08 03:41:12 CDT --- (In reply to comment #3)
Closing.
that's probably a really bad idea, austin, given that it involves data corruption.
l.
http://bugs.winehq.org/show_bug.cgi?id=17390
--- Comment #5 from Alexandre Julliard julliard@winehq.org 2010-09-08 04:29:08 CDT --- (In reply to comment #4)
(In reply to comment #3)
Closing.
that's probably a really bad idea, austin, given that it involves data corruption.
You haven't provided any evidence of an actual problem.
http://bugs.winehq.org/show_bug.cgi?id=17390
--- Comment #6 from Luke Kenneth Casson Leighton lkcl@lkcl.net 2010-09-08 04:48:24 CDT --- (In reply to comment #5)
(In reply to comment #4)
(In reply to comment #3)
Closing.
that's probably a really bad idea, austin, given that it involves data corruption.
You haven't provided any evidence of an actual problem.
true.
and until i receive an apology from the person who told me publicly that i was being "so lazy" whilst spending the time around my birthday two years ago to move wine forward, i'm completely disincentivised to provide any.
sort that out and you might get some assistance from me.
l.
http://bugs.winehq.org/show_bug.cgi?id=17390
--- Comment #7 from Alexandre Julliard julliard@winehq.org 2010-09-08 05:16:46 CDT ---
and until i receive an apology from the person who told me publicly that i was being "so lazy" whilst spending the time around my birthday two years ago to move wine forward, i'm completely disincentivised to provide any.
sort that out and you might get some assistance from me.
I have no idea what you are talking about, but if a silly remark from two years ago is still preventing you from providing useful info, don't come complaining when your bugs get closed as abandoned. This is a bug tracking system, not a psychological helpline.
http://bugs.winehq.org/show_bug.cgi?id=17390
--- Comment #8 from Luke Kenneth Casson Leighton lkcl@lkcl.net 2010-09-08 06:23:35 CDT --- (In reply to comment #7)
and until i receive an apology from the person who told me publicly that i was being "so lazy" whilst spending the time around my birthday two years ago to move wine forward, i'm completely disincentivised to provide any.
sort that out and you might get some assistance from me.
I have no idea what you are talking about, but if a silly remark from two years ago is still preventing you from providing useful info, don't come complaining when your bugs get closed as abandoned. This is a bug tracking system, not a psychological helpline.
1) no individual should have to tolerate their contributions resulting in personal criticisms and attacks. it would appear that in the two years since, the wine team has still not learned to not attack people personally for their contributions, and is intent on continuing to personally attack and criticise contributors.
2) where exactly did you see me "complaining" that this bug was being closed as abandoned? far from "complaining", the comment was made in the interests of the wine project so that an issue of instability was not lost in the noise. absolutely nothing to do with me, personally, and everything to do with furthering the wine project.
3) on that basis, please apologise for your thoughtless and accusatory remark.
http://bugs.winehq.org/show_bug.cgi?id=17390
--- Comment #9 from Dmitry Timoshkov dmitry@codeweavers.com 2010-09-08 07:06:48 CDT --- (In reply to comment #8)
- no individual should have to tolerate their contributions resulting in
personal criticisms and attacks. it would appear that in the two years since, the wine team has still not learned to not attack people personally for their contributions, and is intent on continuing to personally attack and criticise contributors.
It's not very helpful to blame the whole project in this particular bug report considering that there is nothing wrong in the comments and questions posted on this bug towards personally you.
- where exactly did you see me "complaining" that this bug was being closed as
abandoned?
The Comment 4 you posted is really a complain.
far from "complaining", the comment was made in the interests of the wine project so that an issue of instability was not lost in the noise. absolutely nothing to do with me, personally, and everything to do with furthering the wine project.
It is not in the interests of any project to keep a bug report open that doesn't contain any useful information inside.
- on that basis, please apologise for your thoughtless and accusatory remark.
If you would care to re-read all the comments of this bug report an apologize would be appropriate from your side IMHO.
http://bugs.winehq.org/show_bug.cgi?id=17390
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wylda@volny.cz
--- Comment #10 from Wylda wylda@volny.cz 2010-09-08 07:17:07 CDT ---
Hi i'm new here :) From my point of view - here is a bug, which was abandoned by original reporter (for whatever reason) and is marked as abandoned. That's correct.
And when nobody else found it during two years, that means fixing could help mostly/only original reporter. So if i would be original reporter, i would only damage myself with such behaviour ;-)
http://bugs.winehq.org/show_bug.cgi?id=17390
--- Comment #11 from Luke Kenneth Casson Leighton lkcl@lkcl.net 2010-09-08 07:26:18 CDT --- (In reply to comment #9)
(In reply to comment #8)
- no individual should have to tolerate their contributions resulting in
personal criticisms and attacks. it would appear that in the two years since, the wine team has still not learned to not attack people personally for their contributions, and is intent on continuing to personally attack and criticise contributors.
It's not very helpful to blame the whole project
i'm sorry that you believe i am placing blame on the whole project.
in this particular bug report considering that there is nothing wrong in the comments and questions posted on this bug towards personally you.
i'm sorry to hear that you believe that there is no personal criticism made.
- where exactly did you see me "complaining" that this bug was being closed as
abandoned?
The Comment 4 you posted is really a complain.
i'm sorry that you believe it to be a complaint.
far from "complaining", the comment was made in the interests of the wine project so that an issue of instability was not lost in the noise. absolutely nothing to do with me, personally, and everything to do with furthering the wine project.
It is not in the interests of any project to keep a bug report open that doesn't contain any useful information inside.
i'm sorry that you believe that there is no useful information.
i'm sorry that i cannot provide any more useful information.
i'm sorry that i am in such a deeply difficult financial situation that i cannot spare any time or money or energy on providing more information. if you would like to help out by correcting that situation, by providing money in return for providing information, i will be able to assist.
- on that basis, please apologise for your thoughtless and accusatory remark.
If you would care to re-read all the comments of this bug report an apologize would be appropriate from your side IMHO.
i'm sorry that you believe that. please do let me know what you would like me to apologise for and i will do so, because i am completely at a loss to understand the difficulty.
http://bugs.winehq.org/show_bug.cgi?id=17390
--- Comment #12 from Luke Kenneth Casson Leighton lkcl@lkcl.net 2010-09-08 07:40:47 CDT --- (In reply to comment #9) (In reply to comment #10)
Hi i'm new here :) From my point of view - here is a bug, which was abandoned by original reporter (for whatever reason) and is marked as abandoned. That's correct.
And when nobody else found it during two years, that means fixing could help mostly/only original reporter.
hiya wyida,
your comments are particularly interesting, and i apologise that there is insufficient context such that it appears to be the case.
yes, that would be the case... _if_ the "original reporter" was spending their time on personal projects, personally making money for themselves out of the work.
that is, however, entirely an assumption, and in fact the software being installed and improved at the time was entirely free software, and the work being carried out was entirely for the benefit of free software users and for the benefit of the free software community.
it is therefore very unfortunate that one of the wine developers chose to call me "lazy", and i had hoped that the matters which caused them to make such accusations would have resolved itself by now, but it appears that it has not. thus i must once again be the person who highlights these matters to the attention of another group of free software developers, and be the "lightning rod" which somehow, for some reason, encourages people to attack me, and thus they learn, through being shocked by their own behaviour, not to do it again, not to me and not to anyone else, ever again.
i apologise for this, but this has happened so many times now that i'm getting used to being treated like shit, and later - _much_ later - people working out where they behaved incredibly badly.
-
wine-bugs＠winehq.org