1. 19 6月, 2009 3 次提交
  2. 16 6月, 2009 1 次提交
    • A
      NLS: update handling of Unicode · 74675a58
      Alan Stern 提交于
      This patch (as1239) updates the kernel's treatment of Unicode.  The
      character-set conversion routines are well behind the current state of
      the Unicode specification: They don't recognize the existence of code
      points beyond plane 0 or of surrogate pairs in the UTF-16 encoding.
      
      The old wchar_t 16-bit type is retained because it's still used in
      lots of places.  This shouldn't cause any new problems; if a
      conversion now results in an invalid 16-bit code then before it must
      have yielded an undefined code.
      
      Difficult-to-read names like "utf_mbstowcs" are replaced with more
      transparent names like "utf8s_to_utf16s" and the ordering of the
      parameters is rationalized (buffer lengths come immediate after the
      pointers they refer to, and the inputs precede the outputs).
      Fortunately the low-level conversion routines are used in only a few
      places; the interfaces to the higher-level uni2char and char2uni
      methods have been left unchanged.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Acked-by: NClemens Ladisch <clemens@ladisch.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      74675a58
  3. 12 6月, 2009 1 次提交
    • C
      push BKL down into ->put_super · 6cfd0148
      Christoph Hellwig 提交于
      Move BKL into ->put_super from the only caller.  A couple of
      filesystems had trivial enough ->put_super (only kfree and NULLing of
      s_fs_info + stuff in there) to not get any locking: coda, cramfs, efs,
      hugetlbfs, omfs, qnx4, shmem, all others got the full treatment.  Most
      of them probably don't need it, but I'd rather sort that out individually.
      Preferably after all the other BKL pushdowns in that area.
      
      [AV: original used to move lock_super() down as well; these changes are
      removed since we don't do lock_super() at all in generic_shutdown_super()
      now]
      [AV: fuse, btrfs and xfs are known to need no damn BKL, exempt]
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      6cfd0148
  4. 03 4月, 2009 1 次提交
  5. 28 3月, 2009 1 次提交
  6. 22 1月, 2009 1 次提交
  7. 06 1月, 2009 1 次提交
  8. 23 10月, 2008 1 次提交
  9. 14 10月, 2008 1 次提交
  10. 27 7月, 2008 1 次提交
  11. 26 7月, 2008 1 次提交
  12. 30 4月, 2008 1 次提交
  13. 29 4月, 2008 1 次提交
  14. 20 3月, 2008 1 次提交
  15. 09 2月, 2008 2 次提交
  16. 08 2月, 2008 1 次提交
  17. 22 10月, 2007 2 次提交
  18. 20 10月, 2007 1 次提交
  19. 17 10月, 2007 3 次提交
  20. 01 8月, 2007 1 次提交
    • K
      isofs: mounting to regular file may succeed · 817794e0
      Kirill Kuvaldin 提交于
      It turned out that mounting a corrupted ISO image to a regular file may
      succeed, e.g.  if an image was prepared as follows:
      
      $ dd if=correct.iso of=bad.iso bs=4k count=8
      
      We then can mount it to a regular file:
      
      # mount -o loop -t iso9660 bad.iso /tmp/file
      
      But mounting it to a directory fails with -ENOTDIR, simply because
      the root directory inode doesn't have S_IFDIR set and the condition
      in graft_tree() is met:
      
      	if (S_ISDIR(nd->dentry->d_inode->i_mode) !=
      	      S_ISDIR(mnt->mnt_root->d_inode->i_mode))
      		return -ENOTDIR
      
      This is because the root directory inode was read from an incorrect
      block. It's supposed to be read from sbi->s_firstdatazone, which is
      an absolute value and gets messed up in the case of an incorrect image.
      
      In order to somehow circumvent this we have to check that the root
      directory inode is actually a directory after all.
      Signed-off-by: NKirill Kuvaldin <kuvkir@epsmu.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      817794e0
  21. 20 7月, 2007 1 次提交
    • P
      mm: Remove slab destructors from kmem_cache_create(). · 20c2df83
      Paul Mundt 提交于
      Slab destructors were no longer supported after Christoph's
      c59def9f change. They've been
      BUGs for both slab and slub, and slob never supported them
      either.
      
      This rips out support for the dtor pointer from kmem_cache_create()
      completely and fixes up every single callsite in the kernel (there were
      about 224, not including the slab allocator definitions themselves,
      or the documentation references).
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      20c2df83
  22. 18 7月, 2007 1 次提交
  23. 17 7月, 2007 2 次提交
  24. 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
  25. 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
  26. 13 2月, 2007 2 次提交
  27. 09 12月, 2006 1 次提交
  28. 08 12月, 2006 2 次提交
  29. 11 10月, 2006 1 次提交
  30. 04 10月, 2006 1 次提交
  31. 30 9月, 2006 1 次提交
    • J
      [PATCH] I/O Error attempting to read last partial block of a file in an ISO9660 file system · fb50ae74
      Joel &amp; Rebecca VanderZee 提交于
      There was an I/O error that prevented reading the last partial block of
      large files in an ISO9660 filesystem.  The error was generated when a file
      comprised more than one section and had a size that was not an exact
      multiple of the filesystem block size.  This patch removes the check (and
      failure) for reading into the last partial block (and possibly beyond) for
      multiple-section files.
      
      It worked in my testing to prevent reading beyond the end of the section;
      my first patch just incremented the sect_size block count for a partial
      block and continued doing the check.  But there is a commment in the source
      code about reading beyond the end of the file to fill a page cache.
      Failing to access beyond the section would prevent reading beyond the end
      of the file.
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      fb50ae74
新手
引导
客服 返回
顶部