From: Christoph Hellwig <hch@infradead.org>
To: Lachlan McIlroy <lachlan@sgi.com>
Cc: xfs@oss.sgi.com, akpm@linux-foundation.org
Subject: Re: [GIT PULL] XFS update for 2.6.28
Date: Wed, 5 Nov 2008 02:33:28 -0500 [thread overview]
Message-ID: <20081105073328.GA16726@infradead.org> (raw)
In-Reply-To: <20081031045737.ECE0E58AE1E9@chook.melbourne.sgi.com>
Now that the pull request was to late can we at least cherry pick some
fixes?
That'd be at least:
> [XFS] Account for allocated blocks when expanding
> [XFS] Fix use-after-free with log and quotas
> [XFS] Unlock inode before calling xfs_idestroy()
> [XFS] Wait for all I/O on truncate to zero file size
and we probably want the log allocation failure handling patch from Dave
that's not in yet, as it is on the regression list.
next prev parent reply other threads:[~2008-11-05 7:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 4:57 [GIT PULL] XFS update for 2.6.28 Lachlan McIlroy
2008-10-31 5:02 ` david
2008-10-31 5:53 ` Steven Noonan
2008-11-05 1:55 ` Lachlan McIlroy
2008-11-05 7:33 ` Christoph Hellwig [this message]
2008-11-06 16:24 ` [xfs] " Russell Cattelan
-- strict thread matches above, loose matches on Subject: below --
2008-11-11 3:58 Lachlan McIlroy
2008-12-05 4:43 Lachlan McIlroy
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=20081105073328.GA16726@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=lachlan@sgi.com \
--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