On Saturday, November 24, 2012 10:01:39 am Attilio Rao wrote:
On Sat, Nov 24, 2012 at 3:08 AM, Ryan Stone ryst...@gmail.com wrote:
Today I saw a spurious witness warning for acquiring duplicate lock of
same type. The root cause is that when running mtx_destroy on a spinlock
that is held by
On Friday, November 23, 2012 10:08:28 PM Ryan Stone wrote:
Today I saw a spurious witness warning for acquiring duplicate lock of
same type. The root cause is that when running mtx_destroy on a spinlock
that is held by the current thread, mtx_destroy calls spinlock_exit()
before calling
On Sat, Nov 24, 2012 at 3:01 PM, Attilio Rao atti...@freebsd.org wrote:
On Sat, Nov 24, 2012 at 3:08 AM, Ryan Stone ryst...@gmail.com wrote:
Today I saw a spurious witness warning for acquiring duplicate lock of
same type. The root cause is that when running mtx_destroy on a spinlock
that is
On Sat, Nov 24, 2012 at 3:08 AM, Ryan Stone ryst...@gmail.com wrote:
Today I saw a spurious witness warning for acquiring duplicate lock of
same type. The root cause is that when running mtx_destroy on a spinlock
that is held by the current thread, mtx_destroy calls spinlock_exit()
before
On Sat, Nov 24, 2012 at 10:01 AM, Attilio Rao atti...@freebsd.org wrote:
I seriously wonder why right now we don't assume the lock is unheld.
There are likely historically reasons for that, but I would like to
know which one are those and eventually fix them out.
FWIK, all the other locking
On Sat, Nov 24, 2012 at 3:46 PM, Ryan Stone ryst...@gmail.com wrote:
On Sat, Nov 24, 2012 at 10:01 AM, Attilio Rao atti...@freebsd.org wrote:
I seriously wonder why right now we don't assume the lock is unheld.
There are likely historically reasons for that, but I would like to
know which
On Sat, Nov 24, 2012 at 3:51 PM, Attilio Rao atti...@freebsd.org wrote:
On Sat, Nov 24, 2012 at 3:46 PM, Ryan Stone ryst...@gmail.com wrote:
On Sat, Nov 24, 2012 at 10:01 AM, Attilio Rao atti...@freebsd.org wrote:
I seriously wonder why right now we don't assume the lock is unheld.
There are
Today I saw a spurious witness warning for acquiring duplicate lock of
same type. The root cause is that when running mtx_destroy on a spinlock
that is held by the current thread, mtx_destroy calls spinlock_exit()
before calling WITNESS_UNLOCK, which opens up a window in which the CPU can
be
