Skip to content
Snippets Groups Projects
Select Git revision
  • bedb0f056faa94e953e7b3da5a77d25e0008364b
  • vme-testing default
  • ci-test
  • master
  • remoteproc
  • am625-sk-ov5640
  • pcal6534-upstreaming
  • lps22df-upstreaming
  • msc-upstreaming
  • imx8mp
  • iio/noa1305
  • vme-next
  • vme-next-4.14-rc4
  • v4.14-rc4
  • v4.14-rc3
  • v4.14-rc2
  • v4.14-rc1
  • v4.13
  • vme-next-4.13-rc7
  • v4.13-rc7
  • v4.13-rc6
  • v4.13-rc5
  • v4.13-rc4
  • v4.13-rc3
  • v4.13-rc2
  • v4.13-rc1
  • v4.12
  • v4.12-rc7
  • v4.12-rc6
  • v4.12-rc5
  • v4.12-rc4
  • v4.12-rc3
32 results

linux

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Abhi Das authored and Andreas Gruenbacher committed
    Apply the outstanding statfs changes in the journal head to the
    master statfs file. Zero out the local statfs file for good measure.
    
    Previously, statfs updates would be read in from the local statfs inode and
    synced to the master statfs inode during recovery.
    
    We now use the statfs updates in the journal head to update the master statfs
    inode instead of reading in from the local statfs inode. To preserve backward
    compatibility with kernels that can't do this, we still need to keep the
    local statfs inode up to date by writing changes to it. At some point in the
    future, we can do away with the local statfs inodes altogether and keep the
    statfs changes solely in the journal.
    
    Signed-off-by: default avatarAbhi Das <adas@redhat.com>
    Signed-off-by: default avatarAndreas Gruenbacher <agruenba@redhat.com>
    bedb0f05
    History
    Name Last commit Last update