1. 31 3月, 2009 6 次提交
    • J
      reiserfs: journaled xattrs · 0ab2621e
      Jeff Mahoney 提交于
      Deadlocks are possible in the xattr code between the journal lock and the
      xattr sems.
      
      This patch implements journalling for xattr operations. The benefit is
      twofold:
       * It gets rid of the deadlock possibility by always ensuring that xattr
         write operations are initiated inside a transaction.
       * It corrects the problem where xattr backing files aren't considered any
         differently than normal files, despite the fact they are metadata.
      
      I discussed the added journal load with Chris Mason, and we decided that
      since xattrs (versus other journal activity) is fairly rare, the introduction
      of larger transactions to support journaled xattrs wouldn't be too big a deal.
      Signed-off-by: NJeff Mahoney <jeffm@suse.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      0ab2621e
    • J
      reiserfs: eliminate per-super xattr lock · d984561b
      Jeff Mahoney 提交于
      With the switch to using inode->i_mutex locking during lookups/creation
      in the xattr root, the per-super xattr lock is no longer needed.
      
      This patch removes it.
      Signed-off-by: NJeff Mahoney <jeffm@suse.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      d984561b
    • J
      reiserfs: remove IS_PRIVATE helpers · 6dfede69
      Jeff Mahoney 提交于
      There are a number of helper functions for marking a reiserfs inode
      private that were leftover from reiserfs did its own thing wrt to
      private inodes.  S_PRIVATE has been in the kernel for some time, so this
      patch removes the helpers and uses IS_PRIVATE instead.
      Signed-off-by: NJeff Mahoney <jeffm@suse.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      6dfede69
    • J
      reiserfs: use reiserfs_error() · 0030b645
      Jeff Mahoney 提交于
      This patch makes many paths that are currently using warnings to handle
      the error.
      Signed-off-by: NJeff Mahoney <jeffm@suse.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      0030b645
    • J
      reiserfs: rework reiserfs_panic · c3a9c210
      Jeff Mahoney 提交于
      ReiserFS panics can be somewhat inconsistent.
      In some cases:
       * a unique identifier may be associated with it
       * the function name may be included
       * the device may be printed separately
      
      This patch aims to make warnings more consistent. reiserfs_warning() prints
      the device name, so printing it a second time is not required. The function
      name for a warning is always helpful in debugging, so it is now automatically
      inserted into the output. Hans has stated that every warning should have
      a unique identifier. Some cases lack them, others really shouldn't have them.
      reiserfs_warning() now expects an id associated with each message. In the
      rare case where one isn't needed, "" will suffice.
      Signed-off-by: NJeff Mahoney <jeffm@suse.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      c3a9c210
    • J
      reiserfs: rework reiserfs_warning · 45b03d5e
      Jeff Mahoney 提交于
      ReiserFS warnings can be somewhat inconsistent.
      In some cases:
       * a unique identifier may be associated with it
       * the function name may be included
       * the device may be printed separately
      
      This patch aims to make warnings more consistent. reiserfs_warning() prints
      the device name, so printing it a second time is not required. The function
      name for a warning is always helpful in debugging, so it is now automatically
      inserted into the output. Hans has stated that every warning should have
      a unique identifier. Some cases lack them, others really shouldn't have them.
      reiserfs_warning() now expects an id associated with each message. In the
      rare case where one isn't needed, "" will suffice.
      Signed-off-by: NJeff Mahoney <jeffm@suse.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      45b03d5e
  2. 01 1月, 2009 1 次提交
  3. 14 11月, 2008 1 次提交
  4. 23 10月, 2008 1 次提交
  5. 28 4月, 2008 1 次提交
  6. 31 3月, 2008 1 次提交
  7. 09 5月, 2007 1 次提交
  8. 13 2月, 2007 1 次提交
  9. 09 12月, 2006 1 次提交
  10. 04 10月, 2006 1 次提交
  11. 01 10月, 2006 3 次提交
  12. 01 7月, 2006 1 次提交
  13. 03 3月, 2006 1 次提交
  14. 02 2月, 2006 1 次提交
  15. 15 1月, 2006 1 次提交
  16. 14 8月, 2005 1 次提交
  17. 13 7月, 2005 1 次提交
    • L
      reiserfs: run scripts/Lindent on reiserfs code · bd4c625c
      Linus Torvalds 提交于
      This was a pure indentation change, using:
      
      	scripts/Lindent fs/reiserfs/*.c include/linux/reiserfs_*.h
      
      to make reiserfs match the regular Linux indentation style.  As Jeff
      Mahoney <jeffm@suse.com> writes:
      
       The ReiserFS code is a mix of a number of different coding styles, sometimes
       different even from line-to-line. Since the code has been relatively stable
       for quite some time and there are few outstanding patches to be applied, it
       is time to reformat the code to conform to the Linux style standard outlined
       in Documentation/CodingStyle.
      
       This patch contains the result of running scripts/Lindent against
       fs/reiserfs/*.c and include/linux/reiserfs_*.h. There are places where the
       code can be made to look better, but I'd rather keep those patches separate
       so that there isn't a subtle by-hand hand accident in the middle of a huge
       patch. To be clear: This patch is reformatting *only*.
      
       A number of patches may follow that continue to make the code more consistent
       with the Linux coding style.
      
       Hans wasn't particularly enthusiastic about these patches, but said he
       wouldn't really oppose them either.
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      bd4c625c
  18. 24 6月, 2005 1 次提交
  19. 06 5月, 2005 1 次提交
  20. 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