From: Jeremy Fitzhardinge <jeremy@goop.org>
To: David Chinner <dgc@sgi.com>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
xfs-masters@oss.sgi.com
Subject: Re: [2/3] 2.6.22-rc1: known regressions v2 - XFS
Date: Wed, 16 May 2007 16:40:20 -0700 [thread overview]
Message-ID: <464B9664.2040200@goop.org> (raw)
In-Reply-To: <20070516233419.GP85884050@sgi.com>
David Chinner wrote:
> Jeremy has tentatively indicated that the patch has fixed the problem.
> Have you seen any more problems since applying the patch, Jeremy?
>
No, it continues to seem sound with casual use; I would have expected to
see the problem reoccur by now. I'd like to rerun the full set of tests
I did before to be sure, but so far so good. No other apparent
regressions either.
Also, the match between the observed symptoms and the bugfix is very
good, which adds confidence (ie, no element of "it works now but we
don't know why"). I guess the only remaining concern is whether there
are any other paths which fail to dirty the inode.
Did you manage to repro the problem?
J
next prev parent reply other threads:[~2007-05-16 23:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <464B6743.9000607@googlemail.com>
2007-05-16 20:31 ` [2/3] 2.6.22-rc1: known regressions v2 Michal Piotrowski
2007-05-16 20:33 ` Christoph Lameter
2007-05-16 20:44 ` Linus Torvalds
2007-05-16 23:34 ` [2/3] 2.6.22-rc1: known regressions v2 - XFS David Chinner
2007-05-16 23:40 ` Jeremy Fitzhardinge [this message]
2007-05-16 23:57 ` David Chinner
[not found] ` <464B6895.60806@googlemail.com>
2007-05-16 20:31 ` [3/3] 2.6.22-rc1: known regressions v2 Michal Piotrowski
2007-05-16 20:31 ` Michal Piotrowski
2007-05-16 20:39 ` Mauro Carvalho Chehab
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=464B9664.2040200@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=xfs-masters@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.