Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Kaz Kylheku <643-408-1753@kylheku.com> Newsgroups: comp.unix.shell,comp.unix.programmer,comp.lang.misc Subject: Re: Python (was Re: I did not inhale) Date: Mon, 19 Aug 2024 04:54:44 -0000 (UTC) Organization: A noiseless patient Spider Lines: 19 Message-ID: <20240818215317.300@kylheku.com> References: <20240408075547.000061e8@gmail.com> <20240412094809.811@kylheku.com> <87il0mm94y.fsf@tudado.org> <87il0lldf8.fsf@tudado.org> <20240815182717.189@kylheku.com> <20240818094145.827@kylheku.com> Injection-Date: Mon, 19 Aug 2024 06:54:44 +0200 (CEST) Injection-Info: dont-email.me; posting-host="896f64b1942145a2d62fd9abf0eabcbc"; logging-data="2896986"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19eWQgxn2ioHyyGJrKd/gNNYd16waw/2hs=" User-Agent: slrn/pre1.0.4-9 (Linux) Cancel-Lock: sha1:KatWZalx3X4kjC4OGLupx5VZnIc= Bytes: 2373 On 2024-08-18, Dmitry A. Kazakov wrote: > On 2024-08-18 18:46, Kaz Kylheku wrote: > >> If a mutex is actually used to protect shared data against concurrent >> access, and the owner dies while holding the mutex, the next thread >> to try to grab the mutex must be informed so it can try to recover >> the shared data into a sane state. > > There is no recovery if a protected operation crashes, because the state > of the object is unknown. That is false; the object's state can be analyzed and repaired. How easily you can do that depends on the data structure and algorithms used to manipulate it. Think of recoverable file systems. -- TXR Programming Language: http://nongnu.org/txr Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal Mastodon: @Kazinator@mstdn.ca