1. 28 3月, 2009 1 次提交
  2. 08 2月, 2008 3 次提交
  3. 22 10月, 2007 1 次提交
  4. 18 7月, 2007 1 次提交
    • C
      knfsd: exportfs: remove iget abuse · 5ca29607
      Christoph Hellwig 提交于
      When the exportfs interface was added the expectation was that filesystems
      provide an operation to convert from a file handle to an inode/dentry, but it
      kept a backwards compat option that still calls into iget.
      
      Calling into iget from non-filesystem code is very bad, because it gives too
      little information to filesystem, and simply crashes if the filesystem doesn't
      implement the ->read_inode routine.
      
      Fortunately there are only two filesystems left using this fallback: efs and
      jfs.  This patch moves a copy of export_iget to each of those to implement the
      get_dentry method.
      
      While this is a temporary increase of lines of code in the kernel it allows
      for a much cleaner interface and important code restructuring in later
      patches.
      
      [akpm@linux-foundation.org: add jfs_get_inode_flags() declaration]
      Signed-off-by: NDave Kleikamp <shaggy@linux.vnet.ibm.com>
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NNeil Brown <neilb@suse.de>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      5ca29607
  5. 25 4月, 2007 1 次提交
  6. 13 2月, 2007 1 次提交
  7. 02 10月, 2006 1 次提交
  8. 27 7月, 2006 1 次提交
  9. 29 6月, 2006 1 次提交
  10. 29 3月, 2006 1 次提交
  11. 09 2月, 2006 1 次提交
    • H
      JFS: ext2 inode attributes for jfs · fa3241d2
      Herbert Poetzl 提交于
      ext2 inode attributes with relevance for jfs:
      
      'a' 	EXT2_APPEND_FL       -> append only
      'i' 	EXT2_IMMUTABLE_FL    -> immutable file
      's' 	EXT2_SECRM_FL	     -> zero file
      'u' 	EXT2_UNRM_FL	     -> allow for unrm
      'A' 	EXT2_NOATIME_FL      -> no access time
      'D' 	EXT2_DIRSYNC_FL      -> dirsync
      'S' 	EXT2_SYNC_FL	     -> sync
      
      overview of jfs flags (partially for OS/2)
      
      value	   (OS/2)	Linux	ext2 attrs
      ------------------------------------------------
      0x00010000 IFJOURNAL	-
      0x00020000 ISPARSE  	used
      0x00040000 INLINEEA 	used
      0x00080000 -	    	-	JFS_NOATIME_FL
      
      0x00100000 -	    	-	JFS_DIRSYNC_FL
      0x00200000 -	    	-	JFS_SYNC_FL
      0x00400000 -	    	-	JFS_SECRM_FL
      0x00800000 ISWAPFILE	-	JFS_UNRM_FL
      
      0x01000000 -	    	-	JFS_APPEND_FL
      0x02000000 IREADONLY	-	JFS_IMMUTABLE_FL
      0x04000000 IHIDDEN  	-	-
      0x08000000 ISYSTEM  	-	-
      
      0x10000000 -	    	-
      0x20000000 IDIRECTORY	used
      0x40000000 IARCHIVE 	-
      0x80000000 INEWNAME 	-
      
      the implementation is straight forward, except
      for the fact that the attributes have to be mapped
      to match with the ext2 ones to avoid a separate
      tool for manipulating them (this could be avoided
      when using a separate flag field in the on-disk
      representation, but the overhead is minimal)
      
      a special jfs_ioctl is added to allow for the new
      JFS_IOC_GETFLAGS and JFS_IOC_SETFLAGS calls.
      
      a helper function jfs_set_inode_flags() to transfer
      the flags from the on-disk version to the inode
      
      minor changes to allow flag inheritance on inode
      creation, as well as a cleanup of the on-disk
      flags (including the new ones)
      
      beforementioned helper to map between ext2 and jfs
      versions of the new flags ...
      
      the JFS_SECRM_FL and JFS_UNRM_FL are not done yet
      and I'm not 100% sure they are worth the effort,
      the rest seems to work out of the box ...
      Signed-off-by: NHerbert Poetzl <herbert@13thfloor.at>
      Signed-off-by: NDave Kleikamp <shaggy@austin.ibm.com>
      fa3241d2
  12. 05 5月, 2005 1 次提交
  13. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4