Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • linux
  • Repository
You need to sign in or sign up before continuing.
  • linux
  • kernel
  • workqueue.c
Find file BlameHistoryPermalink
  • Lai Jiangshan's avatar
    workqueue: Put PWQ allocation and WQ enlistment in the same lock C.S. · 1726a171
    Lai Jiangshan authored Jul 04, 2024
    
    
    The PWQ allocation and WQ enlistment are not within the same lock-held
    critical section; therefore, their states can become out of sync when
    the user modifies the unbound mask or if CPU hotplug events occur in
    the interim since those operations only update the WQs that are already
    in the list.
    
    Make the PWQ allocation and WQ enlistment atomic.
    
    Signed-off-by: default avatarLai Jiangshan <jiangshan.ljs@antgroup.com>
    Signed-off-by: default avatarTejun Heo <tj@kernel.org>
    1726a171
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7