[Jaunty] SRU: Selective backport of 7 ext4 patches

Stefan Bader stefan.bader at canonical.com
Thu Aug 27 14:02:36 UTC 2009


SRU Justification:

After examining the ext4 maintainer's 2.6.28-stable tree repository there were 
a few candidate patches we should consider backporting. These will prevent some 
cases of Oops', lock contention, file corruption, CPU lockups, memory leaks, 
and fsck errors.

Fix: A selective backport of 7 patches with high impact. See the pull request 
or link to gitweb.

Testcase: While unable to reproduce the cases, I ran the fs test suite proposed 
in https://lists.ubuntu.com/archives/kernel-team/2009-June/006147.html before 
and after applying the patchset and could see no degression.

---

http://kernel.ubuntu.com/git?p=smb/ubuntu-jaunty.git;a=shortlog;h=refs/heads/bug418197

The following changes since commit 5dbbcb81f3124fbdaef51f6874531f5dbc343886:
   Scott Moser (1):
         include drivers/pci/hotplug/* in -virtual package

are available in the git repository at:

   git://kernel.ubuntu.com/smb/ubuntu-jaunty.git bug418197

Aneesh Kumar K.V (2):
       ext4: Fix sub-block zeroing for writes into preallocated extents
       jbd2: Call journal commit callback without holding j_list_lock

Dan Carpenter (1):
       ext4: fix typo which causes a memory leak on error path

Eric Sandeen (3):
       ext4: don't call jbd2_journal_force_commit_nested without journal
       ext4: fix ext4_free_inode() vs. ext4_claim_inode() race
       ext4: fix bogus BUG_ONs in in mballoc code

Theodore Ts'o (1):
       ext4: Fix softlockup caused by illegal i_file_acl value in on-disk inode

  fs/ext4/balloc.c     |    4 +++-
  fs/ext4/extents.c    |    2 ++
  fs/ext4/ialloc.c     |    8 +++++---
  fs/ext4/inode.c      |   21 ++++++++++++++++++++-
  fs/ext4/mballoc.c    |    6 +++---
  fs/jbd2/checkpoint.c |    2 +-
  fs/jbd2/commit.c     |   13 ++++++++-----
  include/linux/jbd2.h |    4 ++--
  8 files changed, 44 insertions(+), 16 deletions(-)

-- 

When all other means of communication fail, try words!






More information about the kernel-team mailing list