1. 13 2月, 2007 2 次提交
  2. 12 2月, 2007 1 次提交
  3. 31 12月, 2006 1 次提交
  4. 09 12月, 2006 1 次提交
  5. 01 10月, 2006 2 次提交
  6. 27 9月, 2006 1 次提交
  7. 11 7月, 2006 1 次提交
    • D
      [PATCH] NOMMU: Fix execution off of ramfs with mmap() · 21ff8216
      David Howells 提交于
      Fix execution through the FDPIC binfmt of programs stored on ramfs by
      preventing the ramfs mmap() returning successfully on a private mapping of
      a ramfs file.  This causes NOMMU mmap to make a copy of the mapped portion
      of the file and map that instead.
      
      This could be improved by granting direct mapping access to read-only
      private mappings for which the data is stored on a contiguous run of pages.
       However, this is only likely to be the case if the file was extended with
      truncate before being written.
      
      ramfs is left to map the file directly for shared mappings so that SYSV IPC
      and POSIX shared memory both still work.
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Cc: Hugh Dickins <hugh@veritas.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      21ff8216
  8. 29 6月, 2006 1 次提交
  9. 23 6月, 2006 1 次提交
    • D
      [PATCH] VFS: Permit filesystem to override root dentry on mount · 454e2398
      David Howells 提交于
      Extend the get_sb() filesystem operation to take an extra argument that
      permits the VFS to pass in the target vfsmount that defines the mountpoint.
      
      The filesystem is then required to manually set the superblock and root dentry
      pointers.  For most filesystems, this should be done with simple_set_mnt()
      which will set the superblock pointer and then set the root dentry to the
      superblock's s_root (as per the old default behaviour).
      
      The get_sb() op now returns an integer as there's now no need to return the
      superblock pointer.
      
      This patch permits a superblock to be implicitly shared amongst several mount
      points, such as can be done with NFS to avoid potential inode aliasing.  In
      such a case, simple_set_mnt() would not be called, and instead the mnt_root
      and mnt_sb would be set directly.
      
      The patch also makes the following changes:
      
       (*) the get_sb_*() convenience functions in the core kernel now take a vfsmount
           pointer argument and return an integer, so most filesystems have to change
           very little.
      
       (*) If one of the convenience function is not used, then get_sb() should
           normally call simple_set_mnt() to instantiate the vfsmount. This will
           always return 0, and so can be tail-called from get_sb().
      
       (*) generic_shutdown_super() now calls shrink_dcache_sb() to clean up the
           dcache upon superblock destruction rather than shrink_dcache_anon().
      
           This is required because the superblock may now have multiple trees that
           aren't actually bound to s_root, but that still need to be cleaned up. The
           currently called functions assume that the whole tree is rooted at s_root,
           and that anonymous dentries are not the roots of trees which results in
           dentries being left unculled.
      
           However, with the way NFS superblock sharing are currently set to be
           implemented, these assumptions are violated: the root of the filesystem is
           simply a dummy dentry and inode (the real inode for '/' may well be
           inaccessible), and all the vfsmounts are rooted on anonymous[*] dentries
           with child trees.
      
           [*] Anonymous until discovered from another tree.
      
       (*) The documentation has been adjusted, including the additional bit of
           changing ext2_* into foo_* in the documentation.
      
      [akpm@osdl.org: convert ipath_fs, do other stuff]
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Acked-by: NAl Viro <viro@zeniv.linux.org.uk>
      Cc: Nathan Scott <nathans@sgi.com>
      Cc: Roland Dreier <rolandd@cisco.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      454e2398
  10. 29 3月, 2006 1 次提交
  11. 23 3月, 2006 1 次提交
  12. 22 3月, 2006 1 次提交
  13. 07 3月, 2006 1 次提交
  14. 25 2月, 2006 1 次提交
  15. 07 1月, 2006 1 次提交
    • D
      [PATCH] NOMMU: Provide shared-writable mmap support on ramfs · 642fb4d1
      David Howells 提交于
      The attached patch makes ramfs support shared-writable mmaps by:
      
       (1) Attempting to perform a contiguous block allocation to the requested size
           when truncate attempts to increase the file from zero size, such as
           happens when:
      
      	fd = shm_open("/file/on/ramfs", ...):
      	ftruncate(fd, size_requested);
      	addr = mmap(NULL, subsize, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_SHARED,
      		    fd, offset);
      
       (2) Permitting any shared-writable mapping over any contiguous set of extant
           pages. get_unmapped_area() will return the address into the actual ramfs
           pages. The mapping may start anywhere and be of any size, but may not go
           over the end of file. Multiple mappings may overlap in any way.
      
       (3) Not permitting a file to be shrunk if it would truncate any shared
           mappings (private mappings are copied).
      
      Thus this patch provides support for POSIX shared memory on NOMMU kernels,
      with certain limitations such as there being a large enough block of pages
      available to support the allocation and it only working on directly mappable
      filesystems.
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      642fb4d1
  16. 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