1. 11 7月, 2009 1 次提交
  2. 12 6月, 2009 1 次提交
  3. 08 6月, 2009 1 次提交
  4. 04 6月, 2009 1 次提交
  5. 14 11月, 2008 1 次提交
  6. 07 11月, 2008 4 次提交
  7. 03 8月, 2008 1 次提交
  8. 27 7月, 2008 1 次提交
    • M
      [patch 3/4] fat: dont call notify_change · b1da47e2
      Miklos Szeredi 提交于
      The FAT_IOCTL_SET_ATTRIBUTES ioctl() calls notify_change() to change
      the file mode before changing the inode attributes.  Replace with
      explicit calls to security_inode_setattr(), fat_setattr() and
      fsnotify_change().
      
      This is equivalent to the original.  The reason it is needed, is that
      later in the series we move the immutable check into notify_change().
      That would break the FAT_IOCTL_SET_ATTRIBUTES ioctl, as it needs to
      perform the mode change regardless of the immutability of the file.
      
      [Fix error if fat is built as a module.  Thanks to OGAWA Hirofumi for
      noticing.]
      Signed-off-by: NMiklos Szeredi <mszeredi@suse.cz>
      Acked-by: NOGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      b1da47e2
  9. 03 7月, 2008 1 次提交
  10. 21 6月, 2008 1 次提交
    • L
      Replace BKL with superblock lock in fat/msdos/vfat · 8f593427
      Linus Torvalds 提交于
      This replaces the use of the BKL in the FAT family of filesystems with the
      existing superblock lock instead.
      
      The code already appears to do mostly proper locking with its own private
      spinlocks (and mutexes), but while the BKL could possibly have been
      dropped entirely, converting it to use the superblock lock (which is just
      a regular mutex) is the conservative thing to do.
      
      As a per-filesystem mutex, it not only won't have any of the possible
      latency issues related to the BKL, but the lock is obviously private to
      the particular filesystem instance and will thus not cause problems for
      entirely unrelated users like the BKL can.
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
      Signed-off-by: NJonathan Corbet <corbet@lwn.net>
      8f593427
  11. 13 6月, 2008 1 次提交
  12. 30 4月, 2008 1 次提交
  13. 28 4月, 2008 3 次提交
  14. 19 4月, 2008 1 次提交
  15. 07 2月, 2008 1 次提交
    • J
      fs/fat/: refine chmod checks · 19c561a6
      Jan Engelhardt 提交于
      Prohibit mode changes in non-quiet mode that cannot be stored reliably with
      the on-disk format.
      
      Suppose a vfat filesystem is mounted with umask=0 and [not-quiet].  Then
      all files will have mode 0777.  Trying to change the owner will fail,
      because fat does not know about owners or groups.  chmod 0770, on the other
      hand, will succeed, even though fat does not know about the permission
      triplet [user/group/other].
      
      So this patch changes fat's not-quiet behavior so that only UNIX modes are
      accepted that can be mapped lossless between the fat disk format and the
      local system.  There is only one attribute, and that is the readonly
      attribute, which is mapped to the UNIX write permission bit(s).  chmod 0555
      is therefore valid (taking away the +w bits <=> setting the readonly
      attribute).  Since chmod 0775 and chmod 0755 is an ambiguous case as to
      whether to set or clear the readonly bit, these modes are also denied.
      
      In quiet mode, chmod and chown will continue to "succeed" as they did
      before, meaning that a subsequent stat() will temporarily return the new
      mode as long as the inode is not reread from disk, and chown will silently
      do nothing, not even return the new uid/gid in stat().
      Signed-off-by: NJan Engelhardt <jengelh@computergmbh.de>
      Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      19c561a6
  16. 10 7月, 2007 1 次提交
  17. 13 2月, 2007 1 次提交
  18. 09 12月, 2006 1 次提交
  19. 17 11月, 2006 1 次提交
  20. 21 10月, 2006 1 次提交
    • A
      [PATCH] separate bdi congestion functions from queue congestion functions · 3fcfab16
      Andrew Morton 提交于
      Separate out the concept of "queue congestion" from "backing-dev congestion".
      Congestion is a backing-dev concept, not a queue concept.
      
      The blk_* congestion functions are retained, as wrappers around the core
      backing-dev congestion functions.
      
      This proper layering is needed so that NFS can cleanly use the congestion
      functions, and so that CONFIG_BLOCK=n actually links.
      
      Cc: "Thomas Maier" <balagi@justmail.de>
      Cc: "Jens Axboe" <jens.axboe@oracle.com>
      Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
      Cc: David Howells <dhowells@redhat.com>
      Cc: Peter Osterlund <petero2@telia.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      3fcfab16
  21. 01 10月, 2006 1 次提交
  22. 30 9月, 2006 1 次提交
  23. 29 3月, 2006 1 次提交
  24. 04 2月, 2006 1 次提交
  25. 12 1月, 2006 1 次提交
  26. 10 1月, 2006 1 次提交
  27. 09 1月, 2006 2 次提交
  28. 18 9月, 2005 1 次提交
  29. 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