1. 04 4月, 2014 1 次提交
  2. 10 5月, 2011 3 次提交
  3. 23 10月, 2010 2 次提交
  4. 20 11月, 2009 6 次提交
  5. 14 9月, 2009 1 次提交
  6. 10 6月, 2009 3 次提交
    • R
      nilfs2: allow future expansion of metadata read out via get info ioctl · 003ff182
      Ryusuke Konishi 提交于
      Nilfs has some ioctl commands to read out metadata from meta data
      files:
      
       - NILFS_IOCTL_GET_CPINFO for checkpoint file,
       - NILFS_IOCTL_GET_SUINFO for segment usage file, and
       - NILFS_IOCTL_GET_VINFO for Disk Address Transalation (DAT) file,
         respectively.
      
      Every routine on these metadata files is implemented so that it allows
      future expansion of on-disk format.  But, the above ioctl commands do
      not support expansion even though nilfs_argv structure can handle
      arbitrary size for data exchanged via ioctl.
      
      This allows future expansion of the following structures which give
      basic format of the "get information" ioctls:
      
       - struct nilfs_cpinfo
       - struct nilfs_suinfo
       - struct nilfs_vinfo
      
      So, this introduces forward compatility of such ioctl commands.
      
      In this patch, a sanity check in nilfs_ioctl_get_info() function is
      changed to accept larger data structure [1], and metadata read
      routines are rewritten so that they become compatible for larger
      structures; the routines will just ignore the remaining fields which
      the current version of nilfs doesn't know.
      
      [1] The ioctl function already has another upper limit (PAGE_SIZE
          against a structure, which appears in nilfs_ioctl_wrap_copy
          function), and this will not cause security problem.
      Signed-off-by: NRyusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
      003ff182
    • R
      nilfs2: eliminate removal list of segments · 071cb4b8
      Ryusuke Konishi 提交于
      This will clean up the removal list of segments and the related
      functions from segment.c and ioctl.c, which have hurt code
      readability.
      
      This elimination is applied by using nilfs_sufile_updatev() previously
      introduced in the patch ("nilfs2: add sufile function that can modify
      multiple segment usages").
      Signed-off-by: NRyusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
      071cb4b8
    • R
      nilfs2: add sufile function that can modify multiple segment usages · dda54f4b
      Ryusuke Konishi 提交于
      This is a preparation for the later cleanup patch ("nilfs2: remove
      list of freeing segments").
      
      This adds nilfs_sufile_updatev() to sufile, which can modify multiple
      segment usages at a time.
      Signed-off-by: NRyusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
      dda54f4b
  7. 13 4月, 2009 2 次提交
    • R
      nilfs2: fix possible mismatch of sufile counters on recovery · c85399c2
      Ryusuke Konishi 提交于
      On-disk counters ndirtysegs and ncleansegs of sufile, can go wrong
      after roll-forward recovery because
      nilfs_prepare_segment_for_recovery() function marks segments dirty
      without adjusting value of these counters.
      
      This fixes the problem by adding a function to sufile which does the
      operation adjusting the counters, and by letting the recovery function
      use it.
      Signed-off-by: NRyusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
      c85399c2
    • R
      nilfs2: segment usage file cleanups · a703018f
      Ryusuke Konishi 提交于
      This will simplify sufile.c by sharing common code which repeatedly
      appears in routines updating a segment usage entry; a wrapper function
      nilfs_sufile_update() is introduced for the purpose, and counter
      modifications are integrated to a new function
      nilfs_sufile_mod_counter().
      
      This is a preparation for the successive bugfix patch ("nilfs2: fix
      possible mismatch of sufile counters on recovery").
      Signed-off-by: NRyusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
      a703018f
  8. 07 4月, 2009 1 次提交