Re: Detect double-release of spinlock
От | Andres Freund |
---|---|
Тема | Re: Detect double-release of spinlock |
Дата | |
Msg-id | 20240729174853.uo5qjqkxlacjg6vv@awork3.anarazel.de обсуждение исходный текст |
Ответ на | Re: Detect double-release of spinlock (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Detect double-release of spinlock
Re: Detect double-release of spinlock |
Список | pgsql-hackers |
Hi, On 2024-07-29 13:25:22 -0400, Tom Lane wrote: > Heikki Linnakangas <hlinnaka@iki.fi> writes: > > Yeah I'm not worried about that at all. Also, the assert is made when > > you have already released the spinlock; you are already out of the > > critical section. > > Not in the patch Andres posted. Which seems fairly fundamental - once outside of the critical section, we can't actually assert that the lock isn't acquired, somebody else *validly* might have acquired it by then. 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. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: