From: Federico Sevilla III <jijo@fs3.ph>
To: xfs@oss.sgi.com
Subject: Re: [PATCH] Possible fix for 2.6.24 xfs_file_readdir crash
Date: Mon, 11 Feb 2008 14:35:25 +0800 [thread overview]
Message-ID: <1202711725.4679.7.camel@humanitas.fs3.ph> (raw)
In-Reply-To: <20080211001727.GO155407@sgi.com>
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
On Mon, 2008-02-11 at 11:17 +1100, David Chinner wrote:
> > Can we reckon that this patch will get included in one of the next
> > minor releases?
>
> Already queued for 2.6.24.2.
2.6.24.2 has been released to address the vmsplice issue. Unfortunately,
no other changes seem to have been included. Hopefully, the
xfs_file_readdir patch will make it to 2.6.24.3.
--
Federico Sevilla III
F S 3 Consulting Inc.
http://www.fs3.ph
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-02-11 6:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 5:24 [PATCH] Possible fix for 2.6.24 xfs_file_readdir crash David Chinner
2008-02-06 4:55 ` Christoph Hellwig
2008-02-06 9:46 ` Tobias Ulmer
2008-02-06 9:59 ` .:deadhead:.
2008-02-09 12:04 ` Sven Geggus
2008-02-11 0:17 ` David Chinner
2008-02-11 6:35 ` Federico Sevilla III [this message]
2008-02-13 0:46 ` Jason White
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=1202711725.4679.7.camel@humanitas.fs3.ph \
--to=jijo@fs3.ph \
--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