Date: Sun, 25 Sep 2016 19:37:15 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212168] [panic] [UFS] use-after-free panic (0xdeadc0dedeadc0de) 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/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212168 --- 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. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-212168-3630-fIJclmRS6S>