[SERVER-8103] Verify js ($eval/$where/MR) cannot access db context outside of current db Created: 07/Jan/13  Updated: 08/Jan/13  Resolved: 08/Jan/13

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

Type: Task Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File authmr.js    
Participants:

 Description   

We need to check if the global write lock is still required for these.



 Comments   
Comment by Andy Schwerin [ 08/Jan/13 ]

Actually, change of heart. This bug doesn't really describe the locking problem I'm thinking of. This really is a dupe of SERVER-8104.

Comment by Andy Schwerin [ 08/Jan/13 ]

Not quite the same. SERVER-8104 is about a security hole. Despite the summary, this one is really more about overly strong locking. Solving this probably depends on resolving SERVER-8104, but would not be solved by it.

Comment by Eliot Horowitz (Inactive) [ 08/Jan/13 ]

Seems to be the same as SERVER-8104

Comment by Andy Schwerin [ 07/Jan/13 ]

Run the following to demonstrate the bug:

buildscripts/smoke.py --nopreallocj jstests/sharding/authmr.js 

The --nopreallocj is optional.

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