Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • I ipipe-arm64
  • Project information
    • Project information
    • Activity
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • xenomai
  • ipipe-arm64
  • Repository

Switch branch/tag
  • ipipe-arm64
  • drivers
  • thunderbolt
  • switch.c
Find file BlameHistoryPermalink
  • Mika Westerberg's avatar
    thunderbolt: Correct access permissions for active NVM contents · 800161bd
    Mika Westerberg authored Jun 29, 2017
    
    
    Firmware upgrade tools that decide which NVM image should be uploaded to
    the Thunderbolt controller need to access active parts of the NVM even
    if they are not run as root. The information in active NVM is not
    considered security critical so we can use the default permissions set
    by the NVMem framework.
    
    Writing the NVM image is still left as root only operation.
    
    While there mark the active NVM as read-only in the filesystem.
    Reported-by: default avatarYehezkel Bernat <yehezkel.bernat@intel.com>
    Signed-off-by: default avatarMika Westerberg <mika.westerberg@linux.intel.com>
    Signed-off-by: default avatarAndreas Noever <andreas.noever@gmail.com>
    Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
    800161bd

Replace switch.c

Attach a file by drag & drop or click to upload


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

Imprint & Privacy Policy