From owner-freebsd-fs@freebsd.org  Sun Sep 25 19:37:16 2016
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id C14C9BE95C3
 for <freebsd-fs@mailman.ysv.freebsd.org>; Sun, 25 Sep 2016 19:37:16 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B0DBA642
 for <freebsd-fs@FreeBSD.org>; Sun, 25 Sep 2016 19:37:16 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8PJbFQp093400
 for <freebsd-fs@FreeBSD.org>; Sun, 25 Sep 2016 19:37:16 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 212168] [panic] [UFS] use-after-free panic (0xdeadc0dedeadc0de)
Date: Sun, 25 Sep 2016 19:37:15 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-RC1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: kib@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-212168-3630-fIJclmRS6S@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-212168-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-212168-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Sep 2016 19:37:16 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212168

--- Comment #17 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to Andrew Turner from comment #16)
Ok.

If you copy/paste WORKLIST_INSERT_UNLOCKED and only add the barrier there, =
does
the issue disappear as well ?

There is only one use of WORKLIST_INSERT_UNLOCKED in the ffs_softdep.c, and=
 no
uses of WORKLIST_REMOVE_UNLOCKED at all.  All other calls are for
WORKLIST_INSERT/REMOVE(), which assert that the mount point' softdep lock is
owned.  Of course, it might be some other access for read which is not under
softdep lock.

The only use of WORKLIST_INSERT_UNLOCKED() is for the ffs_blkfree(), where =
some
local worklist is formed from the items.  The list is processed in the same
thread (passed to softdep_setup_blkfree()) in ffs_blkfree()->ffs_blkfree_cg=
()
for !TRIM case.

--=20
You are receiving this mail because:
You are the assignee for the bug.=