1. 09 2月, 2008 14 次提交
  2. 17 10月, 2007 2 次提交
  3. 31 8月, 2007 1 次提交
  4. 01 8月, 2007 1 次提交
  5. 22 7月, 2007 1 次提交
  6. 20 7月, 2007 2 次提交
  7. 18 7月, 2007 1 次提交
  8. 01 6月, 2007 1 次提交
    • Y
      parse errors in ifdefs · f8343685
      Yoann Padioleau 提交于
      Fix various bits of obviously-busted code which we're not happening to
      compile, due to ifdefs.
      
      Cc: "Luck, Tony" <tony.luck@intel.com>
      Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
      Cc: Richard Henderson <rth@twiddle.net>
      Cc: Russell King <rmk@arm.linux.org.uk>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Cc: Jeff Garzik <jeff@garzik.org>
      Cc: Jan Kara <jack@ucw.cz>
      Cc: James Bottomley <James.Bottomley@steeleye.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      f8343685
  9. 17 5月, 2007 1 次提交
    • C
      Remove SLAB_CTOR_CONSTRUCTOR · a35afb83
      Christoph Lameter 提交于
      SLAB_CTOR_CONSTRUCTOR is always specified. No point in checking it.
      Signed-off-by: NChristoph Lameter <clameter@sgi.com>
      Cc: David Howells <dhowells@redhat.com>
      Cc: Jens Axboe <jens.axboe@oracle.com>
      Cc: Steven French <sfrench@us.ibm.com>
      Cc: Michael Halcrow <mhalcrow@us.ibm.com>
      Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
      Cc: Miklos Szeredi <miklos@szeredi.hu>
      Cc: Steven Whitehouse <swhiteho@redhat.com>
      Cc: Roman Zippel <zippel@linux-m68k.org>
      Cc: David Woodhouse <dwmw2@infradead.org>
      Cc: Dave Kleikamp <shaggy@austin.ibm.com>
      Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
      Cc: "J. Bruce Fields" <bfields@fieldses.org>
      Cc: Anton Altaparmakov <aia21@cantab.net>
      Cc: Mark Fasheh <mark.fasheh@oracle.com>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Christoph Hellwig <hch@lst.de>
      Cc: Jan Kara <jack@ucw.cz>
      Cc: David Chinner <dgc@sgi.com>
      Cc: "David S. Miller" <davem@davemloft.net>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      a35afb83
  10. 09 5月, 2007 4 次提交
  11. 08 5月, 2007 1 次提交
    • C
      slab allocators: Remove SLAB_DEBUG_INITIAL flag · 50953fe9
      Christoph Lameter 提交于
      I have never seen a use of SLAB_DEBUG_INITIAL.  It is only supported by
      SLAB.
      
      I think its purpose was to have a callback after an object has been freed
      to verify that the state is the constructor state again?  The callback is
      performed before each freeing of an object.
      
      I would think that it is much easier to check the object state manually
      before the free.  That also places the check near the code object
      manipulation of the object.
      
      Also the SLAB_DEBUG_INITIAL callback is only performed if the kernel was
      compiled with SLAB debugging on.  If there would be code in a constructor
      handling SLAB_DEBUG_INITIAL then it would have to be conditional on
      SLAB_DEBUG otherwise it would just be dead code.  But there is no such code
      in the kernel.  I think SLUB_DEBUG_INITIAL is too problematic to make real
      use of, difficult to understand and there are easier ways to accomplish the
      same effect (i.e.  add debug code before kfree).
      
      There is a related flag SLAB_CTOR_VERIFY that is frequently checked to be
      clear in fs inode caches.  Remove the pointless checks (they would even be
      pointless without removeal of SLAB_DEBUG_INITIAL) from the fs constructors.
      
      This is the last slab flag that SLUB did not support.  Remove the check for
      unimplemented flags from SLUB.
      Signed-off-by: NChristoph Lameter <clameter@sgi.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      50953fe9
  12. 13 2月, 2007 1 次提交
  13. 08 12月, 2006 3 次提交
  14. 06 10月, 2006 1 次提交
  15. 30 9月, 2006 1 次提交
    • E
      [PATCH] mount udf UDF_PART_FLAG_READ_ONLY partitions with MS_RDONLY · 39b3f6d6
      Eric Sandeen 提交于
      There's a bug where a UDF_PART_FLAG_READ_ONLY udf partition gets mounted
      read-write, then subsequent problems happen; files seem to be able to be
      removed, but file creation results in EIO or worse, oops.
      
      EIO is coming from udf_new_block(), which returns EIO if the right flags
      aren't set; only UDF_PART_FLAG_READ_ONLY is set in this case.  We probably
      s hould not have gotten this far...
      
      Attached patch seems to fix it - and includes a printk to alert the user
      that their "rw" mount request has been converted to "ro."
      
      Here's the testcase I used:
      
      [root@magnesium ~]# mkisofs -R -J -udf -o testiso /tmp/
      ...
      Total translation table size: 0
      Total rockridge attributes bytes: 342923
      Total directory bytes: 382312
      Path table size(bytes): 104
      Max brk space used 103000
      105059 extents written (205 MB)
      
      [root@magnesium ~]# mount -o loop testiso /mnt/test/
      [root@magnesium ~]# ls /mnt/test/fsfile
      /mnt/test/fsfile
      [root@magnesium ~]# rm /mnt/test/fsfile
      [root@magnesium ~]# ls /mnt/test/fsfile
      ls: /mnt/test/fsfile: No such file or directory
      [root@magnesium ~]# touch /mnt/test/fsfile
      touch: cannot touch `/mnt/test/fsfile': Input/output error
      [root@magnesium tmp]# grep udf /proc/mounts
      /dev/loop1 /mnt/test udf rw 0 0
      
      Force readonly mounts of UDF partitions marked as read-only.
      Signed-off-by: NEric Sandeen <sandeen@sandeen.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      39b3f6d6
  16. 27 9月, 2006 1 次提交
  17. 23 8月, 2006 1 次提交
  18. 15 8月, 2006 1 次提交
    • D
      [PATCH] initialize parts of udf inode earlier in create · 95f8797f
      Dan Bastone 提交于
      Eric says:
      
      > I saw an oops down this path when trying to create a new file on a UDF
      > filesystem which was internally marked as readonly, but mounted rw:
      >
      > udf_create
      >         udf_new_inode
      >                 new_inode
      >                         alloc_inode
      >                         	udf_alloc_inode
      >                 udf_new_block
      >                         returns EIO due to readonlyness
      >                 iput (on error)
      
      I ran into the same issue today, but when listing a directory with
      invalid/corrupt entries:
      
      udf_lookup
              udf_iget
                      get_new_inode_fast
                              alloc_inode
                                      udf_alloc_inode
                      __udf_read_inode
                              fails for any reason
                      iput (on error)
                              ...
      
      The following patch to udf_alloc_inode() should take care of both (and
      other similar) cases, but I've only tested it with udf_lookup().
      Signed-off-by: NDan Bastone <dan@pwienterprises.com>
      Cc: Eric Sandeen <sandeen@sandeen.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      95f8797f
  19. 01 7月, 2006 1 次提交
  20. 23 6月, 2006 1 次提交