[SERVER-19929] Audit sharding code for potential use-after-frees Created: 13/Aug/15  Updated: 25/Sep/15  Resolved: 25/Sep/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.1.6
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Kamran K. Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: 32qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-20559 Race condition in shard registry duri... Closed
related to SERVER-20629 Use-after-free in CatalogManagerRepli... Closed
is related to SERVER-19367 Segfault establishing shard connectio... Closed
is related to SERVER-19839 Use-after-free in ShardRegistry::runC... Closed
is related to SERVER-18815 Shard object lifetime shoud be manage... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 9 (09/18/15), Sharding A (10/09/15)
Participants:
Linked BF Score: 0

 Description   

There have been at least 3 crashes in sharding code caused by use-after-frees or the misuse of references in the 3.1.x cycle: SERVER-19367, SERVER-19839, and SERVER-18815 (the last commit)

We should proactively search for similar issues to avoid costly debugging later.



 Comments   
Comment by Andy Schwerin [ 25/Sep/15 ]

All discovered use-after-frees involve the shared pointers to Shard type, and are covered by separate tickets.

Generated at Thu Feb 08 03:52:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.