linux-ext4 - [Bug 60788] xfstest generic/068 failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 22 Jul 2015 18:37:26 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 60788] xfstest generic/068 failure - kernel BUG at
 fs/buffer.c:3005!

https://bugzilla.kernel.org/show_bug.cgi?id=60788

Eric Whitney <enwlinux@...il.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #2 from Eric Whitney <enwlinux@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html