From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 60788] xfstest generic/068 failure - kernel BUG at fs/buffer.c:3005!
Date: Wed, 22 Jul 2015 18:37:26 +0000 [thread overview]
Message-ID: <bug-60788-13602-05j9uy3fpC@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60788-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60788
Eric Whitney <enwlinux@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Eric Whitney <enwlinux@gmail.com> ---
This bug is a duplicate of #60786.
A patch included in 4.2-rc1 has resolved this problem: "ext4: fix race between
truncate and __ext4_journalled_writepage()" (bdf96838aea6)
The method used to force the bug to occur in the past was to make repeated runs
of generic/068 on a test filesystem mounted with the data=journal option. The
test system would typically hang with a few tens of runs at the most.
1000 test runs completed normally both on x86_64 and 32 bit ARM running 4.2-rc1
kernels. Regular regression runs containing generic/068 have also completed
normally using 4.2-rc2 and -rc3 kernels on the same architectures.
*** This bug has been marked as a duplicate of bug 60786 ***
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2015-07-22 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-24 19:02 [Bug 60788] New: xfstest generic/068 failure - kernel BUG at fs/buffer.c:3005! bugzilla-daemon
2014-03-23 11:39 ` [Bug 60788] " bugzilla-daemon
2015-07-22 18:37 ` bugzilla-daemon [this message]
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=bug-60788-13602-05j9uy3fpC@https.bugzilla.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 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.