Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • X xcap-capability-linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • xcap
  • xcap-capability-linux
  • Repository

Switch branch/tag
  • xcap-capability-linux
  • fs
  • proc
  • internal.h
Find file BlameHistoryPermalink
  • Alexey Dobriyan's avatar
    proc 1/2: do PDE usecounting even for ->read_proc, ->write_proc · 3dec7f59
    Alexey Dobriyan authored Feb 20, 2009
    struct proc_dir_entry::owner is going to be removed. Now it's only necessary
    to protect PDEs which are using ->read_proc, ->write_proc hooks.
    
    However, ->owner assignments are racy and make it very easy for someone to switch
    ->owner on live PDE (as some subsystems do) without fixing refcounts and so on.
    
    http://bugzilla.kernel.org/show_bug.cgi?id=12454
    
    
    
    So, ->owner is on death row.
    
    Proxy file operations exist already (proc_file_operations), just bump usecount
    when necessary.
    Signed-off-by: default avatarAlexey Dobriyan <adobriyan@gmail.com>
    3dec7f59

Replace internal.h

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.