From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12579] ext4 filesystem hang
Date: Thu, 12 Feb 2009 08:37:04 -0800 (PST) [thread overview]
Message-ID: <20090212163704.3CADE108047@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12579-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12579
------- Comment #2 from aneesh.kumar@linux.vnet.ibm.com 2009-02-12 08:37 -------
Two commits which are already in the mainline which fixed some changes
after .28 are
89e1219004b3657cc014521663eeef0744f1c99d
dcf6a79dda5cc2a2bec183e50d829030c0972aaa
Both changes have implication wrt ext4. I would suggest try with the
above two commits and see if the problem still exist.
-aneesh
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-02-12 16:37 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
2009-02-12 16:37 ` bugme-daemon [this message]
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=20090212163704.3CADE108047@picon.linux-foundation.org \
--to=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 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.