From: Dave Chinner <david@fromorbit.com>
To: Chris Torek <chris.torek@windriver.com>
Cc: xfs@oss.sgi.com
Subject: Re: question about xfs_fsync on linux
Date: Tue, 15 Jul 2008 12:48:30 +1000 [thread overview]
Message-ID: <20080715024830.GZ29319@disturbed> (raw)
In-Reply-To: <200807150129.m6F1THE23901@elf.torek.net>
On Mon, Jul 14, 2008 at 07:29:16PM -0600, Chris Torek wrote:
> >What kernel(s), exactly, is/are showing this problem?
>
> Well, that part is a bit tricky. The base kernel is 2.6.21
> but it has a lot of patches, including the one you mentioned.
> (The customer is double checking to make sure they actually have
> that patch in.)
Well, you are pretty much on your own, then. Really, we cannot help
diagnose problems on old kernels with a random set of backported
patches in them. If you can provide a reproducable test case that
triggers the problem on a recent, pristine tree then we can find the
problem and fix it.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-07-15 2:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 22:13 question about xfs_fsync on linux Chris Torek
2008-07-14 23:03 ` Dave Chinner
2008-07-15 1:29 ` Chris Torek
2008-07-15 2:48 ` Dave Chinner [this message]
2008-07-16 21:58 ` Chris Torek
2008-07-17 0:22 ` Dave Chinner
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=20080715024830.GZ29319@disturbed \
--to=david@fromorbit.com \
--cc=chris.torek@windriver.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