kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

Strange, I see that the commit that fixes this bug was applied to
mainline twice.  Once in v3.5-rc4 and then again in v3.6-rc1:

76d0953 xfs: fix allocbt cursor leak in xfs_alloc_ag_vextent_near
079da28 xfs: fix allocbt cursor leak in xfs_alloc_ag_vextent_near

$ git describe --contains 76d0953
v3.5-rc4~7^2~3

$ git describe --contains 079da28
v3.6-rc1~42^2~36


At any rate, neither was cc'd to stable, so the fix will not be in Precise.

I'll build a Precise test kernel with a cherry-pick of commit 079da28.

** Changed in: linux (Ubuntu)
     Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
       Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1327360

Title:
  xfs_btree_cur leak

Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  There appears to be a kernel memory leak of xfs_btree_cur in recent
  Precise kernels (3.2.0-45 and -63 are affected, for sure).   The slab
  can grow unbounded; we've seen it grow larger than 32GB via slabtop.
  The affected hosts have XFS mounted on / (root filesystem).

  We have another host running 3.2.0-38 in which we do not see this
  problem (it has a 37TB XFS filesystem mounted, but not on root).

  Upgrading to the latest 3.8.0-41 kernel via linux-generic-lts-raring
  seems to resolve the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327360/+subscriptions