1. 02 Jun, 2005 2 commits
    • Jan Kara's avatar
      [PATCH] ext3: fix list scanning in __cleanup_transaction · 7e3b11a9
      Jan Kara authored
      
      Fix a bug in list scanning that can cause us to skip the last buffer on the
      checkpoint list (and hence fail to do any progress under some rather
      unfavorable conditions).
      
      The problem is we first do jh=next_jh and then test
      
      	} while (jh!=last_jh);
      
      Hence we skip the last buffer on the list (if it was not the only buffer on
      the list).  As we already do jh=next_jh; in the beginning of the loop we
      are safe to just remove the assignment in the end.  It can happen that 'jh'
      will be freed at the point we test jh != last_jh but that does not matter
      as we never *dereference* the pointer.
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      7e3b11a9
    • Jan Kara's avatar
      [PATCH] ext3: fix log_do_checkpoint() assertion failure · 00ea8145
      Jan Kara authored
      
      Fix possible false assertion failure in log_do_checkpoint().  We might fail
      to detect that we actually made a progress when cleaning up the checkpoint
      lists if we don't retry after writing something to disk.  The patch was
      confirmed to fix observed assertion failures for several users.
      
      When we flushed some buffers we need to retry scanning the list.
      Otherwise we can fail to detect our progress.
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      00ea8145
  2. 01 Jun, 2005 1 commit
    • Benjamin Herrenschmidt's avatar
      [PATCH] ppc32/ppc64: cleanup /proc/device-tree · 5f64f739
      Benjamin Herrenschmidt authored
      
      This cleans up the /proc/device-tree representation of the Open Firmware
      device-tree on ppc and ppc64.  It does the following things:
      
       - Workaround an issue in some Apple device-trees where a property may
         exist with the same name as a child node of the parent.  We now
         simply "drop" the property instead of creating duplicate entries in
         /proc with random result...
      
       - Do not try to chop off the "@0" at the end of a node name whose unit
         address is 0.  This is not useful, inconsistent, and the code was
         buggy and didn't always work anyway.
      
       - Do not create symlinks for the short name and unit address parts of a
         node.  These were never really used, bloated the memory footprint of
         the device-tree with useless struct proc_dir_entry and their matching
         dentry and inode cache bloat.
      
      This results in smaller code, smaller memory footprint, and a more
      accurate view of the tree presented to userland.
      Signed-off-by: default avatarBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      5f64f739
  3. 31 May, 2005 1 commit
  4. 28 May, 2005 1 commit
  5. 27 May, 2005 1 commit
  6. 21 May, 2005 1 commit
  7. 19 May, 2005 1 commit
  8. 18 May, 2005 1 commit
    • Stephen Tweedie's avatar
      [PATCH] Avoid console spam with ext3 aborted journal. · 30121624
      Stephen Tweedie authored
      
      Avoid console spam with ext3 aborted journal.
      
      ext3 usually reports error conditions that it detects in its environment.
      But when its journal gets aborted due to such errors, it can sometimes
      continue to report that condition forever, spamming the console to such
      an extent that the initial first cause of the journal abort can be lost.
      
      When the journal aborts, we put the filesystem into readonly mode.  Most
      subsequent filesystem operations will get rejected immediately by checks
      for MS_RDONLY either in the filesystem or in the VFS.  But some paths do
      not have such checks --- for example, if we continue to write to a file
      handle that was opened before the fs went readonly.  (We only check for
      the ROFS condition when the file is first opened.)  In these cases, we
      can continue to generate log errors similar to
      
      EXT3-fs error (device $DEV) in start_transaction: Journal has aborted
      
      for each subsequent write.
      
      There is really no point in generating these errors after the initial
      error has been fully reported.  Specifically, if we're starting a
      completely new filesystem operation, and the filesystem is *already*
      readonly (ie. the ext3 layer has already detected and handled the
      underlying jbd abort), and we see an EROFS error, then there is simply
      no point in reporting it again.
      Signed-off-by: default avatarStephen Tweedie <sct@redhat.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      30121624
  9. 17 May, 2005 6 commits
  10. 07 May, 2005 1 commit
    • Andrew Morton's avatar
      [PATCH] revert msdos partitioning fix · b2411dd2
      Andrew Morton authored
      
      This change from March 3rd causes the partition parsing code to ignore
      partitions which have a signature byte of zero.  Turns out that more people
      have such partitions than we expected, and their device numbering is coming up
      wrong in post-2.6.11 kernels.
      
      So revert the change while we think about the problem a bit more.
      
      Cc: Andries Brouwer <Andries.Brouwer@cwi.nl>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      b2411dd2
  11. 06 May, 2005 2 commits
  12. 05 May, 2005 22 commits