From: Lee Revell <rlrevell@joe-job.com>
To: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Jan De Luyck <lkml@kcore.org>,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: [2.6.10-rc2] XFS filesystem corruption
Date: Tue, 23 Nov 2004 14:13:43 -0500 [thread overview]
Message-ID: <1101237223.6358.10.camel@krustophenia.net> (raw)
In-Reply-To: <41A30D3E.9090506@gmx.de>
On Tue, 2004-11-23 at 11:13 +0100, Prakash K. Cheemplavam wrote:
> Is xfs known to be broken while preempt is on? (Esp
> using ck's preemp big kernel lock?)
Minor nitpick: Ingo wrote the preempt BKL code, not Con.
Lee
next prev parent reply other threads:[~2004-11-23 19:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 14:30 [2.6.10-rc2] XFS filesystem corruption Jan De Luyck
2004-11-22 15:51 ` William Lee Irwin III
2004-11-23 10:13 ` Prakash K. Cheemplavam
2004-11-23 19:13 ` Lee Revell [this message]
2004-11-23 19:22 ` Prakash K. Cheemplavam
2004-11-23 21:27 ` Nathan Scott
2004-11-24 8:04 ` Prakash K. Cheemplavam
2004-11-24 12:50 ` Eric Sandeen
2004-11-25 7:28 ` Prakash K. Cheemplavam
2004-11-22 23:34 ` Eric Sandeen
2004-11-23 6:36 ` Jan De Luyck
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=1101237223.6358.10.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=lkml@kcore.org \
--cc=prakashkc@gmx.de \
--cc=wli@holomorphy.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