Re: Detect double-release of spinlock

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Detect double-release of spinlock
Date: 2024-07-29 17:57:02
Message-ID: 2812470.1722275822@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> However, I still don't think it's a problem to assert that the lock is held in
> in the unlock "routine". As mentioned before, the spinlock implementation
> itself has never followed the "just straight line code" rule that users of
> spinlocks are supposed to follow.

Yeah, that's fair.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2024-07-29 18:00:35 Re: Detect double-release of spinlock
Previous Message Tom Lane 2024-07-29 17:56:05 Re: pgsql: Fix double-release of spinlock

Browse pgsql-hackers by date

  From Date Subject
Next Message Joel Jacobson 2024-07-29 17:57:21 Re: Optimize mul_var() for var1ndigits >= 8
Previous Message Tom Lane 2024-07-29 17:56:05 Re: pgsql: Fix double-release of spinlock