From: Theodore Tso <tytso@mit.edu>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: bugme-daemon@bugzilla.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [Bug 12579] ext4 filesystem hang
Date: Thu, 12 Feb 2009 12:49:08 -0500 [thread overview]
Message-ID: <20090212174908.GA6922@mini-me.lan> (raw)
In-Reply-To: <20090212163610.GA10351@skywalker>
>> Finally had some time, and I've tracked this down to the
>> page-writeback.c changes since .28 - backing them all out the
>> testcase runs overnight. Still working out which one and why. I
>> suppose it's still possible it's an ext4 bug but if so the
>> page-writeback.c changes exposed it.
>>
>> It's a classic deadlock; I usually have 2 threads stuck, pdflush
>> vs. the livecd creator doing an fsync. Each is waiting for a page
>> the other has locked.
>
> Two commits which are already in the mainline which fixed some changes
> after .28 are
>
> 89e1219004b3657cc014521663eeef0744f1c99d
> dcf6a79dda5cc2a2bec183e50d829030c0972aaa
>
I read Eric's email as saying he tracked it down to the
page-writeback.c changes *after* 2.6.28. Eric, is that what you
meant?
- Ted
next prev parent reply other threads:[~2009-02-12 18:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 5:03 [Bug 12579] New: ext4 filesystem hang bugme-daemon
2009-02-12 15:24 ` [Bug 12579] " bugme-daemon
2009-02-12 16:36 ` Aneesh Kumar K.V
2009-02-12 17:49 ` Theodore Tso [this message]
2009-02-12 16:37 ` bugme-daemon
2009-02-12 16:44 ` bugme-daemon
2009-02-12 18:48 ` bugme-daemon
2009-02-12 18:55 ` bugme-daemon
2009-02-13 0:42 ` bugme-daemon
2009-02-13 11:49 ` Aneesh Kumar K.V
2009-02-13 11:50 ` bugme-daemon
2009-02-13 22:06 ` bugme-daemon
2009-02-14 1:50 ` Theodore Tso
2009-02-14 8:40 ` Aneesh Kumar K.V
2009-02-14 9:41 ` Aneesh Kumar K.V
2009-02-14 8:06 ` Aneesh Kumar K.V
2009-02-13 22:22 ` bugme-daemon
2009-02-14 2:07 ` bugme-daemon
2009-02-14 3:52 ` bugme-daemon
2009-02-14 8:07 ` bugme-daemon
2009-02-14 8:40 ` bugme-daemon
2009-02-14 9:42 ` bugme-daemon
2009-02-20 2:31 ` bugme-daemon
2009-02-21 17:35 ` bugme-daemon
2010-02-27 18:29 ` bugzilla-daemon
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=20090212174908.GA6922@mini-me.lan \
--to=tytso@mit.edu \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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).