Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • I ipipe-x86
  • Project information
    • Project information
    • Activity
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Repository
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • xenomaixenomai
  • ipipe-x86
  • Repository
Switch branch/tag
  • ipipe-x86
  • fs
  • fuse
  • file.c
Find file BlameHistoryPermalink
  • Miklos Szeredi's avatar
    fuse: fix hang of single threaded fuseblk filesystem · 5a18ec17
    Miklos Szeredi authored Feb 25, 2011
    
    
    Single threaded NTFS-3G could get stuck if a delayed RELEASE reply
    triggered a DESTROY request via path_put().
    
    Fix this by
    
     a) making RELEASE requests synchronous, whenever possible, on fuseblk
     filesystems
    
     b) if not possible (triggered by an asynchronous read/write) then do
     the path_put() in a separate thread with schedule_work().
    
    Reported-by: default avatarOliver Neukum <oneukum@suse.de>
    Cc: stable@kernel.org
    Signed-off-by: default avatarMiklos Szeredi <mszeredi@suse.cz>
    5a18ec17

Imprint & Privacy Policy