Skip to content
Snippets Groups Projects
  • David Woodhouse's avatar
    5817b9dc
    jffs2: Improve post-mount CRC scan efficiency · 5817b9dc
    David Woodhouse authored
    
    We need to finish doing the CRC checks before we can allow writes to
    happen, and we currently process the inodes in order. This means a call
    to jffs2_get_ino_cache() for each possible inode# up to c->highest_ino.
    
    There may be a lot of lookups which fail, if the inode# space is used
    sparsely. And the inode# space is *often* used sparsely, if a file
    system contains a lot of stuff that was put there in the original
    image, followed by lots of creation and deletion of new files.
    
    Instead of processing them numerically with a lookup each time, just
    walk the hash buckets instead.
    
    [fix locking typo reported by Dan Carpenter]
    Signed-off-by: default avatarDavid Woodhouse <David.Woodhouse@intel.com>
    5817b9dc
    History
    jffs2: Improve post-mount CRC scan efficiency
    David Woodhouse authored
    
    We need to finish doing the CRC checks before we can allow writes to
    happen, and we currently process the inodes in order. This means a call
    to jffs2_get_ino_cache() for each possible inode# up to c->highest_ino.
    
    There may be a lot of lookups which fail, if the inode# space is used
    sparsely. And the inode# space is *often* used sparsely, if a file
    system contains a lot of stuff that was put there in the original
    image, followed by lots of creation and deletion of new files.
    
    Instead of processing them numerically with a lookup each time, just
    walk the hash buckets instead.
    
    [fix locking typo reported by Dan Carpenter]
    Signed-off-by: default avatarDavid Woodhouse <David.Woodhouse@intel.com>
Code owners
Assign users and groups as approvers for specific file changes. Learn more.