1. 19 5月, 2006 1 次提交
  2. 13 5月, 2006 1 次提交
  3. 26 4月, 2006 1 次提交
  4. 07 4月, 2006 1 次提交
    • S
      [GFS2] Fix a ref count bug and other clean ups · b09e593d
      Steven Whitehouse 提交于
      This fixes a ref count bug that sometimes showed up a umount time
      (causing it to hang) but it otherwise mostly harmless. At the same
      time there are some clean ups including making the log operations
      structures const, moving a memory allocation so that its not done
      in the fast path of checking to see if there is an outstanding
      transaction related to a particular glock.
      
      Removes the sd_log_wrap varaible which was updated, but never actually
      used anywhere. Updates the gfs2 ioctl() to run without the kernel lock
      (which it never needed anyway). Removes the "invalidate inodes" loop
      from GFS2's put_super routine. This is done in kill super anyway so
      we don't need to do it here. The loop was also bogus in that if there
      are any inodes "stuck" at this point its a bug and we need to know
      about it rather than hide it by hanging forever.
      Signed-off-by: NSteven Whitehouse <swhiteho@redhat.com>
      b09e593d
  5. 05 4月, 2006 1 次提交
  6. 01 4月, 2006 2 次提交
    • S
      [GFS2] Update GFS2 for the recent pull from Linus · 8628de05
      Steven Whitehouse 提交于
      Some interfaces have changed. In particular one of the posix
      locking functions has changed prototype, along with the
      address space operation invalidatepage and the block getting
      callback to the direct IO function.
      
      In addition add the splice file operations. These will need to
      be updated to support AOP_TRUNCATED_PAGE before they will be
      of much use to us.
      Signed-off-by: NSteven Whitehouse <swhiteho@redhat.com>
      8628de05
    • S
      [GFS2] Update ioctl() to new interface · 7ea9ea83
      Steven Whitehouse 提交于
      This is designed as a fs independent way to set flags on a
      particular inode. The values of the ioctl() and flags are
      designed to be identical to the ext2/3 values. Assuming that
      this plan is acceptable to people in general, the plan is to
      then move other fs across to using the same set of #defines,
      etc.
      Signed-off-by: NSteven Whitehouse <swhiteho@redhat.com>
      7ea9ea83
  7. 29 3月, 2006 1 次提交
    • S
      [GFS2] Further updates to dir and logging code · 71b86f56
      Steven Whitehouse 提交于
      This reduces the size of the directory code by about 3k and gets
      readdir() to use the functions which were introduced in the previous
      directory code update.
      
      Two memory allocations are merged into one. Eliminates zeroing of some
      buffers which were never used before they were initialised by
      other data.
      
      There is still scope for further improvement in the directory code.
      
      On the logging side, a hand created mutex has been replaced by a
      standard Linux mutex in the log allocation code.
      Signed-off-by: NSteven Whitehouse <swhiteho@redhat.com>
      71b86f56
  8. 22 3月, 2006 1 次提交
  9. 28 2月, 2006 2 次提交
  10. 23 2月, 2006 2 次提交
  11. 21 2月, 2006 1 次提交
  12. 15 2月, 2006 1 次提交
    • S
      [GFS2] Fix for lock recursion problem for internal files · 61a30dcb
      Steven Whitehouse 提交于
      Two internal files which are read through the gfs2_internal_read()
      routine were already locked when the routine was called and this
      do not need locking at the redapages level.
      
      This patch introduces a struct file which is used as a sentinal
      so that readpage will only perform locking in the case that the
      struct file passed to it is _not_ equal to this sentinal.
      
      Since the comments in the generic kernel code indicate that the
      struct file will never be used for anything other than passing
      straight through to readpage(), this should be ok.
      Signed-off-by: NSteven Whitehouse <swhiteho@redhat.com>
      61a30dcb
  13. 14 2月, 2006 1 次提交
    • S
      [GFS2] Put back O_DIRECT support · d1665e41
      Steven Whitehouse 提交于
      This patch adds back O_DIRECT support with various caveats
      attached:
      
       1. Journaled data can be read via O_DIRECT since its now the
          same on disk format as normal data files.
       2. Journaled data writes with O_DIRECT will be failed sliently
          back to normal writes (should we really do this I wonder or
          should we return an error instead?)
       3. Stuffed files will be failed back to normal buffered I/O
       4. All the usual corner cases (write beyond current end of file,
          write to an unallocated block) will also revert to normal buffered I/O.
      
      The I/O path is slightly odd as reads arrive at the page cache layer
      with the lock for the file already held, but writes arrive unlocked.
      Signed-off-by: NSteven Whitehouse <swhiteho@redhat.com>
      d1665e41
  14. 08 2月, 2006 1 次提交
    • S
      [GFS2] Make journaled data files identical to normal files on disk · 18ec7d5c
      Steven Whitehouse 提交于
      This is a very large patch, with a few still to be resolved issues
      so you might want to check out the previous head of the tree since
      this is known to be unstable. Fixes for the various bugs will be
      forthcoming shortly.
      
      This patch removes the special data format which has been used
      up till now for journaled data files. Directories still retain the
      old format so that they will remain on disk compatible with earlier
      releases. As a result you can now do the following with journaled
      data files:
      
       1) mmap them
       2) export them over NFS
       3) convert to/from normal files whenever you want to (the zero length
          restriction is gone)
      
      In addition the level at which GFS' locking is done has changed for all
      files (since they all now use the page cache) such that the locking is
      done at the page cache level rather than the level of the fs operations.
      This should mean that things like loopback mounts and other things which
      touch the page cache directly should now work.
      
      Current known issues:
      
       1. There is a lock mode inversion problem related to the resource
          group hold function which needs to be resolved.
       2. Any significant amount of I/O causes an oops with an offset of hex 320
          (NULL pointer dereference) which appears to be related to a journaled data
          buffer appearing on a list where it shouldn't be.
       3. Direct I/O writes are disabled for the time being (will reappear later)
       4. There is probably a deadlock between the page lock and GFS' locks under
          certain combinations of mmap and fs operation I/O.
       5. Issue relating to ref counting on internally used inodes causes a hang
          on umount (discovered before this patch, and not fixed by it)
       6. One part of the directory metadata is different from GFS1 and will need
          to be resolved before next release.
      Signed-off-by: NSteven Whitehouse <swhiteho@redhat.com>
      18ec7d5c
  15. 18 1月, 2006 2 次提交
  16. 17 1月, 2006 1 次提交