1. 05 1月, 2019 1 次提交
  2. 31 10月, 2018 2 次提交
  3. 23 8月, 2018 1 次提交
  4. 29 1月, 2018 1 次提交
  5. 18 11月, 2017 1 次提交
  6. 28 9月, 2016 1 次提交
  7. 09 5月, 2016 1 次提交
  8. 23 1月, 2016 1 次提交
    • A
      wrappers for ->i_mutex access · 5955102c
      Al Viro 提交于
      parallel to mutex_{lock,unlock,trylock,is_locked,lock_nested},
      inode_foo(inode) being mutex_foo(&inode->i_mutex).
      
      Please, use those for access to ->i_mutex; over the coming cycle
      ->i_mutex will become rwsem, with ->lookup() done with it held
      only shared.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      5955102c
  9. 21 1月, 2016 1 次提交
  10. 21 11月, 2015 1 次提交
  11. 17 4月, 2015 1 次提交
  12. 01 11月, 2014 1 次提交
  13. 29 6月, 2013 1 次提交
  14. 30 4月, 2013 1 次提交
  15. 23 2月, 2013 1 次提交
  16. 21 12月, 2012 1 次提交
  17. 10 10月, 2012 1 次提交
  18. 06 10月, 2012 4 次提交
  19. 31 7月, 2012 1 次提交
  20. 01 6月, 2012 1 次提交
    • N
      fat: use fat_msg_ratelimit() in fat__get_entry() · f0aac616
      Namjae Jeon 提交于
      If an application tries to lookup (opendir/readdir/stat) 5000 files on a
      fatfs USB device and the device is unplugged, many message occur, shown
      below.  This makes the application slow.  So use the new
      fat_msg_ratelimit() decrease the messaging rate.
      
        #> ./file_lookup_testcase ./files_directory/
        usb 2-1.4: USB disconnect, device number 4
        FAT-fs (sda1): FAT read failed (blocknr 2631)
        FAT-fs (sda1): Directory bread(block 396816) failed
        FAT-fs (sda1): Directory bread(block 396817) failed
        FAT-fs (sda1): Directory bread(block 396818) failed
        FAT-fs (sda1): Directory bread(block 396819) failed
        FAT-fs (sda1): Directory bread(block 396820) failed
        FAT-fs (sda1): Directory bread(block 396821) failed
        FAT-fs (sda1): Directory bread(block 396822) failed
        FAT-fs (sda1): Directory bread(block 396823) failed
        FAT-fs (sda1): Directory bread(block 406824) failed
        FAT-fs (sda1): Directory bread(block 406825) failed
        FAT-fs (sda1): Directory bread(block 406826) failed
        FAT-fs (sda1): Directory bread(block 406827) failed
        FAT-fs (sda1): Directory bread(block 406828) failed
        FAT-fs (sda1): Directory bread(block 406829) failed
        FAT-fs (sda1): Directory bread(block 406830) failed
        FAT-fs (sda1): Directory bread(block 406831) failed
        FAT-fs (sda1): Directory bread(block 417696) failed
        FAT-fs (sda1): Directory bread(block 417697) failed
        FAT-fs (sda1): Directory bread(block 417698) failed
        FAT-fs (sda1): Directory bread(block 417699) failed
        FAT-fs (sda1): Directory bread(block 417700) failed
        FAT-fs (sda1): Directory bread(block 417701) failed
        FAT-fs (sda1): Directory bread(block 417702) failed
        FAT-fs (sda1): Directory bread(block 417703) failed
        FAT-fs (sda1): FAT read failed (blocknr 2631)
        FAT-fs (sda1): Directory bread(block 396816) failed
        FAT-fs (sda1): Directory bread(block 396817) failed
        FAT-fs (sda1): Directory bread(block 396818) failed
        FAT-fs (sda1): Directory bread(block 396819) failed
        FAT-fs (sda1): Directory bread(block 396820) failed
        FAT-fs (sda1): Directory bread(block 396821) failed
      Signed-off-by: NNamjae Jeon <linkinjeon@gmail.com>
      Signed-off-by: NAmit Sahrawat <amit.sahrawat83@gmail.com>
      Acked-by: NOGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      f0aac616
  21. 01 11月, 2011 1 次提交
  22. 17 8月, 2011 1 次提交
  23. 12 4月, 2011 1 次提交
  24. 17 5月, 2010 1 次提交
  25. 16 3月, 2010 1 次提交
  26. 13 7月, 2009 1 次提交
  27. 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
  28. 12 6月, 2009 1 次提交
  29. 04 6月, 2009 1 次提交
  30. 12 11月, 2008 1 次提交
  31. 07 11月, 2008 6 次提交