Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
mesa
mesa
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,361
    • Issues 2,361
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 664
    • Merge Requests 664
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mesa
  • mesamesa
  • Issues
  • #23

Closed
Open
Opened Jun 11, 2019 by Rob Clark@robclark💬Owner

fd_batch unref vs resource unref locking issues..

currently __fd_batch_destroy() does the rather questionable thing of dropping screen lock in order to unref pipe_resources.. mainly because resource_destroy path needs to aquire lock, and we don't have recursive locks.

Probably a better approach is an fd_resource_reference_locked() alternative to pipe_resource_reference() in paths where screen lock is held?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: mesa/mesa#23