Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 137
    • Issues 137
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 27
    • Merge requests 27
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.

  • Librem5
  • linux
  • Repository
Switch branch/tag
  • linux
  • fs
  • f2fs
  • file.c
Find file BlameHistoryPermalink
  • Jaegeuk Kim's avatar
    f2fs: do not skip latest inode information · 19c9c466
    Jaegeuk Kim authored Sep 10, 2014
    
    
    In f2fs_sync_file, if there is no written appended writes, it skips
    to write its node blocks.
    But, if there is up-to-date inode page, we should write it to update
    its metadata during the roll-forward recovery.
    
    Signed-off-by: default avatarJaegeuk Kim <jaegeuk@kernel.org>
    19c9c466