From: Mark Lord <kernel@teksavvy.com>
To: Alex Elder <aelder@sgi.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
xfs@oss.sgi.com, akpm@linux-foundation.org
Subject: Re: [GIT PULL] XFS update for 2.6.38-rc3
Date: Tue, 01 Feb 2011 11:00:33 -0500 [thread overview]
Message-ID: <4D482E21.5040803@teksavvy.com> (raw)
In-Reply-To: <201101311642.p0VGgXTS018851@stout.americas.sgi.com>
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@sgi.com (1):
> xfs: xfs_bmap_add_extent_delay_real should init br_startblock
next prev parent reply other threads:[~2011-02-01 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 16:42 [GIT PULL] XFS update for 2.6.38-rc3 Alex Elder
2011-02-01 16:00 ` Mark Lord [this message]
2011-02-03 0:07 ` Dave Chinner
2011-02-03 22:02 ` Arkadiusz Miskiewicz
2011-02-16 21:50 ` [stable] " Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D482E21.5040803@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=aelder@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox