1. 27 May, 2005 2 commits
  2. 21 May, 2005 1 commit
  3. 19 May, 2005 1 commit
  4. 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>
  5. 17 May, 2005 3 commits
    • Andrew Morton's avatar
      [PATCH] block_read_full_page() get_block() error handling fix · c64610ba
      Andrew Morton authored
      If block_read_full_page() detects an error when running get_block() it will
      run SetPageError(), then it will zero out the block in pagecache and will mark
      the buffer_head uptodate.
      So at the end of readahead we end up with a non-uptodate pagecache page which
      is marked PageError.  But it has uptodate buffers.
      The pagefault code will run ClearPageError, will launch readpage a second time
      and block_read_full_page() will notice the uptodate buffers and will mark the
      page uptodate as well.  We end up with an uptodate, !PageError page full of
      zeros and the error is lost.
      (It seems a little odd that filemap_nopage() runs ClearPageError().  I guess
      all of this adds up to meaning that for each attempted access to the page, the
      pagefault handler will retry the I/O.  Which is good and bad.  If the app is
      ignoring SIGBUS for some reason we could get a lot of back-to-back I/O
      Fix it by not marking the pagecache buffer_head as uptodate if the attempt to
      map that buffer to a disk block failed.
      Credit-to: Qu Fuping <fs@ercist.iscas.ac.cn>
        For reporting the bug and identifying its source.
      Signed-off-by: default avatarQu Fuping <fs@ercist.iscas.ac.cn>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
    • Hugh Dickins's avatar
      [PATCH] fix impossible VmallocChunk · 64d13c00
      Hugh Dickins authored
      VmallocTotal: 34359738367 kB
      VmallocUsed:    266288 kB
      VmallocChunk: 18014366299193295 kB
      is unsettling - x86_64 and some other architectures keep a separate address
      range for modules in vmalloc's vmlist, which /proc/meminfo should pass over.
      Signed-off-by: default avatarHugh Dickins <hugh@veritas.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
    • Greg Kroah-Hartman's avatar
      [PATCH] fix Linux kernel ELF core dump privilege elevation · a84a5059
      Greg Kroah-Hartman authored
      As reported by Paul Starzetz <ihaquer@isec.pl>
      Reference: CAN-2005-1263
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
  6. 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>
  7. 05 May, 2005 31 commits