From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12624] umount hangs after fsstress with data=journal
Date: Wed, 3 Jun 2009 21:51:43 GMT [thread overview]
Message-ID: <200906032151.n53LphAe013929@demeter.kernel.org> (raw)
In-Reply-To: <bug-12624-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12624
--- Comment #5 from Theodore Tso <tytso@mit.edu> 2009-06-03 21:51:42 ---
On Fri, May 22, 2009 at 06:51:43AM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> I guess we would need this patch. But i am still hitting the BUG_ON.
> Will try to debug further later today.
>
> -aneesh
>
> commit 85ddb1581222bac63035c16a6536b0a5a2cd60a0
> Author: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> Date: Thu May 21 23:58:17 2009 +0530
>
> ext4: Don't look at buffer_heads outside i_size.
>
>
> Buffer heads outside i_size will be unmapped. So when we
> are doing "walk_page_buffers" limit ourself to i_size.
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
OK, added to the ext4 patch tree.
- Ted
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2009-06-03 21:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 17:32 [Bug 12624] New: umount hangs after fsstress with data=journal bugme-daemon
2009-05-19 19:16 ` [Bug 12624] " bugzilla-daemon
2009-05-21 12:25 ` bugzilla-daemon
2009-05-22 6:51 ` bugzilla-daemon
2009-06-03 21:51 ` Theodore Tso
2009-05-25 18:21 ` bugzilla-daemon
2009-06-03 21:51 ` bugzilla-daemon [this message]
2009-06-04 6:32 ` bugzilla-daemon
[not found] <bug-12624-13602@https.bugzilla.kernel.org/>
2010-03-25 22:21 ` bugzilla-daemon
2010-03-26 10:00 ` bugzilla-daemon
2011-01-12 19:07 ` 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=200906032151.n53LphAe013929@demeter.kernel.org \
--to=bugzilla-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).