1. 27 Dec, 2012 2 commits
    • Theodore Ts'o's avatar
      ext4: avoid hang when mounting non-journal filesystems with orphan list · 0e9a9a1a
      Theodore Ts'o authored
      When trying to mount a file system which does not contain a journal,
      but which does have a orphan list containing an inode which needs to
      be truncated, the mount call with hang forever in
      ext4_orphan_cleanup() because ext4_orphan_del() will return
      immediately without removing the inode from the orphan list, leading
      to an uninterruptible loop in kernel code which will busy out one of
      the CPU's on the system.
      This can be trivially reproduced by trying to mount the file system
      found in tests/f_orphan_extents_inode/image.gz from the e2fsprogs
      source tree.  If a malicious user were to put this on a USB stick, and
      mount it on a Linux desktop which has automatic mounts enabled, this
      could be considered a potential denial of service attack.  (Not a big
      deal in practice, but professional paranoids worry about such things,
      and have even been known to allocate CVE numbers for such problems.)
      Signed-off-by: default avatar"Theodore Ts'o" <tytso@mit.edu>
      Reviewed-by: default avatarZheng Liu <wenqing.lz@taobao.com>
      Cc: stable@vger.kernel.org
    • Theodore Ts'o's avatar
      ext4: lock i_mutex when truncating orphan inodes · 721e3eba
      Theodore Ts'o authored
      Commit c278531d added a warning when ext4_flush_unwritten_io() is
      called without i_mutex being taken.  It had previously not been taken
      during orphan cleanup since races weren't possible at that point in
      the mount process, but as a result of this c278531d
      , we will now see
      a kernel WARN_ON in this case.  Take the i_mutex in
      ext4_orphan_cleanup() to suppress this warning.
      Reported-by: default avatarAlexander Beregalov <a.beregalov@gmail.com>
      Signed-off-by: default avatar"Theodore Ts'o" <tytso@mit.edu>
      Reviewed-by: default avatarZheng Liu <wenqing.lz@taobao.com>
      Cc: stable@vger.kernel.org
  2. 25 Dec, 2012 6 commits
  3. 21 Dec, 2012 1 commit
    • Jan Kara's avatar
      jbd2: fix assertion failure in jbd2_journal_flush() · d7961c7f
      Jan Kara authored
      The following race is possible between start_this_handle() and someone
      calling jbd2_journal_flush().
      Process A                              Process B
        if (journal->j_barrier_count) # false
        if (!journal->j_running_transaction) { #true
                                               if (journal->j_running_transaction) {
                                                 # false
                                               ... wait for committing trans ...
          if (!journal->j_running_transaction) { # true
            jbd2_get_transaction(journal, new_transaction);
          goto repeat; # eventually blocks on j_barrier_count > 0
                                                 # fails
      We fix the race by rechecking j_barrier_count after reacquiring j_state_lock
      in exclusive mode.
      Reported-by: yjwsignal@empal.com
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      Signed-off-by: default avatar"Theodore Ts'o" <tytso@mit.edu>
      Cc: stable@vger.kernel.org
  4. 20 Dec, 2012 1 commit
  5. 17 Dec, 2012 1 commit
  6. 11 Dec, 2012 1 commit
  7. 10 Dec, 2012 27 commits
  8. 05 Dec, 2012 1 commit