[SERVER-44967] Check new BSONValidate against old one in bson_validate_fuzzer Created: 05/Dec/19 Updated: 29/Oct/23 Resolved: 18/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 4.3.3 |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Geert Bosch |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Execution Team 2019-12-16, Execution Team 2020-01-13, Execution Team 2020-01-27, Execution Team 2020-02-10, Execution Team 2019-12-30, Execution Team 2020-05-04, Execution Team 2020-08-10, Execution Team 2020-08-24 |
| Participants: |
| Description |
|
It is important to ensure that the set of accepted BSON inputs stays consistent, so that any changes made to the accepted BSON format are deliberate. Use the older/slower version of BSONValidate as an Oracle to compare fuzz results against. By invoking both the old and the new versions, the fuzzer will find inputs that trigger an interesting path in one implementation on the other as well. The intention is that this ticket not only prevents accidental change, but also improves the fuzzing quality. |
| Comments |
| Comment by Githook User [ 18/Aug/20 ] |
|
Author: {'name': 'Geert Bosch', 'email': 'geert@mongodb.com', 'username': 'GeertBosch'}Message: |