[SERVER-2448] CmdFileMD5::run() appears to use cursor's current() unsafely Created: 31/Jan/11 Updated: 12/Jul/16 Resolved: 31/Mar/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | 1.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
It looks like we get a BSONObj from a cursor using cursor->current() and then yield. Because the BSONObj is not owned, its memory may be invalidated by another operation. |
| Comments |
| Comment by auto [ 31/Mar/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: fix filemd5 yielding |
| Comment by Eliot Horowitz (Inactive) [ 01/Feb/11 ] |
|
Also, likely not to cause a segfault, just ive an invalid result. |
| Comment by Eliot Horowitz (Inactive) [ 01/Feb/11 ] |
|
not too worried about this since this is only called right after something is added, so super unlikely. |