1. 30 May, 2019 1 commit
  2. 22 Sep, 2016 1 commit
  3. 15 Apr, 2015 1 commit
  4. 12 Apr, 2015 1 commit
  5. 06 May, 2014 2 commits
  6. 12 Sep, 2013 1 commit
  7. 20 Dec, 2012 1 commit
  8. 05 Oct, 2012 1 commit
  9. 24 Jun, 2011 1 commit
  10. 10 Mar, 2011 1 commit
  11. 09 Aug, 2010 3 commits
    • Christoph Hellwig's avatar
      remove inode_setattr · 1025774c
      Christoph Hellwig authored
      Replace inode_setattr with opencoded variants of it in all callers.  This
      moves the remaining call to vmtruncate into the filesystem methods where it
      can be replaced with the proper truncate sequence.
      
      In a few cases it was obvious that we would never end up calling vmtruncate
      so it was left out in the opencoded variant:
      
       spufs: explicitly checks for ATTR_SIZE earlier
       btrfs,hugetlbfs,logfs,dlmfs: explicitly clears ATTR_SIZE earlier
       ufs: contains an opencoded simple_seattr + truncate that sets the filesize just above
      
      In addition to that ncpfs called inode_setattr with handcrafted iattrs,
      which allowed to trim down the opencoded variant.
      Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
      Signed-off-by: default avatarAl Viro <viro@zeniv.linux.org.uk>
      1025774c
    • Christoph Hellwig's avatar
      add missing setattr methods · d39aae9e
      Christoph Hellwig authored
      For the new truncate sequence every filesystem that wants to truncate on-disk
      state needs a seattr method.  Convert the remaining filesystems that implement
      the truncate inode operation to have its own setattr method.
      Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
      Signed-off-by: default avatarAl Viro <viro@zeniv.linux.org.uk>
      d39aae9e
    • Christoph Hellwig's avatar
      get rid of block_write_begin_newtrunc · 155130a4
      Christoph Hellwig authored
      Move the call to vmtruncate to get rid of accessive blocks to the callers
      in preparation of the new truncate sequence and rename the non-truncating
      version to block_write_begin.
      
      While we're at it also remove several unused arguments to block_write_begin.
      Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
      Signed-off-by: default avatarAl Viro <viro@zeniv.linux.org.uk>
      155130a4
  12. 08 Aug, 2010 1 commit
  13. 10 Jul, 2010 1 commit
  14. 28 May, 2010 1 commit
    • Christoph Hellwig's avatar
      rename the generic fsync implementations · 1b061d92
      Christoph Hellwig authored
      We don't name our generic fsync implementations very well currently.
      The no-op implementation for in-memory filesystems currently is called
      simple_sync_file which doesn't make too much sense to start with,
      the the generic one for simple filesystems is called simple_fsync
      which can lead to some confusion.
      
      This patch renames the generic file fsync method to generic_file_fsync
      to match the other generic_file_* routines it is supposed to be used
      with, and the no-op implementation to noop_fsync to make it obvious
      what to expect.  In addition add some documentation for both methods.
      Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
      Signed-off-by: default avatarAl Viro <viro@zeniv.linux.org.uk>
      1b061d92
  15. 01 Oct, 2009 1 commit
  16. 22 Sep, 2009 2 commits
  17. 12 Jun, 2009 1 commit
  18. 15 Aug, 2008 1 commit
  19. 30 Jul, 2008 1 commit
    • Harvey Harrison's avatar
      omfs: sparse annotations · d406f66d
      Harvey Harrison authored
      Missing cpu_to_be64 on some constant assignments.
      fs/omfs/dir.c:107:16: warning: incorrect type in assignment (different base types)
      fs/omfs/dir.c:107:16:    expected restricted __be64 [usertype] i_sibling
      fs/omfs/dir.c:107:16:    got unsigned long long
      fs/omfs/file.c:33:13: warning: incorrect type in assignment (different base types)
      fs/omfs/file.c:33:13:    expected restricted __be64 [usertype] e_next
      fs/omfs/file.c:33:13:    got unsigned long long
      fs/omfs/file.c:36:24: warning: incorrect type in assignment (different base types)
      fs/omfs/file.c:36:24:    expected restricted __be64 [usertype] e_cluster
      fs/omfs/file.c:36:24:    got unsigned long long
      fs/omfs/file.c:37:23: warning: incorrect type in assignment (different base types)
      fs/omfs/file.c:37:23:    expected restricted __be64 [usertype] e_blocks
      fs/omfs/file.c:37:23:    got unsigned long long
      
      fs/omfs/bitmap.c:74:18: warning: incorrect type in argument 2 (different signedness)
      fs/omfs/bitmap.c:74:18:    expected unsigned long volatile *addr
      fs/omfs/bitmap.c:74:18:    got long *<noident>
      fs/omfs/bitmap.c:77:20: warning: incorrect type in argument 2 (different signedness)
      fs/omfs/bitmap.c:77:20:    expected unsigned long volatile *addr
      fs/omfs/bitmap.c:77:20:    got long *<noident>
      fs/omfs/bitmap.c:112:17: warning: incorrect type in argument 2 (different signedness)
      fs/omfs/bitmap.c:112:17:    expected unsigned long volatile *addr
      fs/omfs/bitmap.c:112:17:    got long *<noident>
      Signed-off-by: default avatarHarvey Harrison <harvey.harrison@gmail.com>
      Acked-by: default avatarBob Copeland <me@bobcopeland.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      d406f66d
  20. 26 Jul, 2008 1 commit