From: "Jörn Engel" <joern@lazybastard.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
David Chinner <dgc@sgi.com>
Subject: Re: [PATCH 2/2] introduce I_SYNC
Date: Tue, 8 May 2007 14:00:40 +0200 [thread overview]
Message-ID: <20070508120037.GB20637@lazybastard.org> (raw)
In-Reply-To: <1178609028.3042.275.camel@localhost.localdomain>
On Tue, 8 May 2007 09:23:48 +0200, Thomas Gleixner wrote:
> On Tue, 2007-05-08 at 00:01 +0200, Jörn Engel wrote:
> > This patch is actually independent of LogFS. It fixes a deadlock
> > hidden in fs/fs-writeback.c that LogFS was unlucky enough to trigger.
> > I strongly suspect NTFS triggered the same deadlock and "solved" it by
> > introducing iget5_nowait(). For LogFS, iget5_nowait() would translate
> > the deadlock into data corruption, so that is not an option.
>
> Have you talked to NTFS folks about that ?
Anton was on Cc: when I sent the first round of this patch. He didn't
respond.
> If it is a general problem, then please seperate the patch from logfs.
The problem certainly is generic and the patch already seperate. I can
resend it in a seperate thread if that is preferred.
Until yesterday it appeared as if LogFS was the only code that could
trigger the problem. NTFS is hard to judge without maintainer comment.
By now it appears as if JFS and NFS have joined in. Maybe I was
over-cautious in not sending it for some month.
Jörn
--
He that composes himself is wiser than he that composes a book.
-- B. Franklin
next prev parent reply other threads:[~2007-05-08 12:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 21:59 [PATCH 0/2] LogFS take two Jörn Engel
2007-05-07 22:00 ` [PATCH 1/2] LogFS proper Jörn Engel
2007-05-07 22:10 ` Jörn Engel
2007-05-07 22:11 ` Jörn Engel
2007-05-08 7:22 ` Thomas Gleixner
2007-05-08 12:46 ` Jan Engelhardt
2007-05-08 15:54 ` Thomas Gleixner
2007-05-08 16:17 ` Evgeniy Polyakov
2007-05-09 13:06 ` Jan Engelhardt
2007-05-08 16:32 ` Jörn Engel
2007-05-08 18:00 ` Thomas Gleixner
2007-05-08 20:25 ` Jörn Engel
2007-05-08 20:58 ` Thomas Gleixner
2007-05-08 21:30 ` Jörn Engel
2007-05-08 19:15 ` Pekka Enberg
2007-05-08 20:58 ` Jörn Engel
2007-05-08 22:52 ` Greg KH
2007-05-08 23:10 ` Jörn Engel
2007-05-09 0:01 ` Greg KH
2007-05-09 10:24 ` Jörn Engel
2007-05-08 22:44 ` Ingo Oeser
2007-05-08 23:05 ` Jörn Engel
2007-05-07 22:01 ` [PATCH 2/2] introduce I_SYNC Jörn Engel
2007-05-08 7:23 ` Thomas Gleixner
2007-05-08 12:00 ` Jörn Engel [this message]
2007-05-08 7:39 ` [PATCH 0/2] LogFS take two Thomas Gleixner
2007-05-08 11:41 ` Jörn Engel
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=20070508120037.GB20637@lazybastard.org \
--to=joern@lazybastard.org \
--cc=akpm@osdl.org \
--cc=dgc@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).