[SERVER-26160] DistLockManager deferred unlock stores StringData objects which may point to invalid memory Created: 19/Sep/16  Updated: 19/Nov/16  Resolved: 19/Sep/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.3.12
Fix Version/s: 3.3.14

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2016-10-10
Participants:
Linked BF Score: 0

 Description   

The dist lock manager's deferred unlock feature stores StringData objects, which is incorrect, because they do not own their memory.

Instead these should be std::string.



 Comments   
Comment by Githook User [ 19/Sep/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-26160 Store std::string in ReplSetDistLockManager instead of StringData
Branch: master
https://github.com/mongodb/mongo/commit/69c7bd7247639e143d21db25460d33667224a8b1

Generated at Thu Feb 08 04:11:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.