[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D482E21.5040803@teksavvy.com>
Date: Tue, 01 Feb 2011 11:00:33 -0500
From: Mark Lord <kernel@...savvy.com>
To: Alex Elder <aelder@....com>
CC: torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
xfs@....sgi.com, akpm@...ux-foundation.org
Subject: Re: [GIT PULL] XFS update for 2.6.38-rc3
On 11-01-31 11:42 AM, Alex Elder wrote:
> Linus, please accept the following updates for XFS, for 2.6.38-rc3
> (if it's not too late) or 2.6.38-rc4.
>
> They are all fixes for bugs that have some pretty undesirable
> consequences. They address:
> - One spot in which a hang can occur due to neglecting to drop a
> lock
> - A bug which in some cases a bogus block number can be recorded in
> a block map btree, resulting in a subsequent BUG_ON().
> - Two memory leaks
> - Three places in which extent sizes are allowed to exceed various
> size limits
> - One place where code depends on behavior that is not well-defined
> by the C standard
> - One problem in handling transaction commit errors
Are these bugs all new in 2.6.38, or should some of these fixes
also go out to -stable for earlier revisions?
> Dave Chinner (8):
> xfs: fix log ticket leak on forced shutdown.
> xfs: fix efi item leak on forced shutdown
> xfs: speculative delayed allocation uses rounddown_power_of_2 badly
> xfs: limit extent length for allocation to AG size
> xfs: prevent extsize alignment from exceeding maximum extent size
> xfs: limit extsize to size of AGs and/or MAXEXTLEN
> xfs: handle CIl transaction commit failures correctly
> xfs: fix dquot shaker deadlock
>
> bpm@....com (1):
> xfs: xfs_bmap_add_extent_delay_real should init br_startblock
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists