public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: "Joël Krähemann" <jkraehemann@gmail.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: libc-help@sourceware.org
Subject: Re: pthread_mutex_timedlock() vs. clock_settime()
Date: Mon, 1 Aug 2022 10:28:30 +0200	[thread overview]
Message-ID: <CA+Owze7UUFq-jqaGdiHMacBx5BykEHn1USLnoCrSge2XXQLcMg@mail.gmail.com> (raw)
In-Reply-To: <deca758d-727c-e812-6a1d-e227585847a1@embedded-brains.de>

Hi,

pthread_mutex_t mtx of struct test_context.

You lock it in line 503 first, then you call test_timeout_finite(),
which calls event_post() in run() second lock.

cheers,
Joël

On Mon, Aug 1, 2022 at 9:52 AM Sebastian Huber
<sebastian.huber@embedded-brains.de> wrote:
>
> Hello Joël,
>
> On 01/08/2022 09:10, Joël Krähemann wrote:
> > Hi Sebastian,
> >
> > You have a dead-lock, probably. I just looked at your code. You are
> > using non-recursive mutices and I think this mutex was locked twice by
> > the very same thread.
>
> thanks for having a look at the test case. Sorry for being so blind, but
> which mutex is where in the code locked twice by the same thread?
>
> If I omit the mutex test case by starting with ACTION_CND_WAIT:
>
>    for (action = ACTION_CND_WAIT; action < ACTION_TERMINATE; ++action) {
>      event_post(&ctx->action, action);
>
> Then the test runs fine:
>
> *** timeout finite ***
> pthread_cond_timedwait
> wake up
> pthread_cond_timedwait: actual 'Connection timed out', expected
> 'Connection timed out'
> pthread_rwlock_timedrdlock
> wake up
> pthread_rwlock_timedrdlock: actual 'Connection timed out', expected
> 'Connection timed out'
> pthread_rwlock_timedwrlock
> wake up
> pthread_rwlock_timedwrlock: actual 'Connection timed out', expected
> 'Connection timed out'
> sem_timedwait
> wake up
> sem_timedwait: actual 'Connection timed out', expected 'Connection timed
> out'
> mq_send
> mq_timedsend
> wake up
> mq_timedsend: actual 'Connection timed out', expected 'Connection timed out'
> mq_receive
> mq_timedreceive
> wake up
> mq_timedreceive: actual 'Connection timed out', expected 'Connection
> timed out'
> clock_nanosleep
> wake up
> clock_nanosleep: actual 'Success', expected 'Success'
>
> --
> embedded brains GmbH
> Herr Sebastian HUBER
> Dornierstr. 4
> 82178 Puchheim
> Germany
> email: sebastian.huber@embedded-brains.de
> phone: +49-89-18 94 741 - 16
> fax:   +49-89-18 94 741 - 08
>
> Registergericht: Amtsgericht München
> Registernummer: HRB 157899
> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> Unsere Datenschutzerklärung finden Sie hier:
> https://embedded-brains.de/datenschutzerklaerung/

  reply	other threads:[~2022-08-01  8:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02  8:43 Sebastian Huber
2022-08-01  7:10 ` Joël Krähemann
2022-08-01  7:41   ` Joël Krähemann
2022-08-03 23:44   ` Sebastian Huber
2022-08-01  8:28     ` Joël Krähemann [this message]
2022-08-01  8:36       ` Sebastian Huber
2022-08-01  9:51         ` Joël Krähemann
2022-08-01 11:51           ` Joël Krähemann
2022-08-01 11:59             ` Joël Krähemann
2022-08-01 14:44               ` Joël Krähemann
2022-08-01 16:31             ` Sebastian Huber
2022-08-01 20:11               ` Joël Krähemann
2022-08-01 22:05                 ` Joël Krähemann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+Owze7UUFq-jqaGdiHMacBx5BykEHn1USLnoCrSge2XXQLcMg@mail.gmail.com \
    --to=jkraehemann@gmail.com \
    --cc=libc-help@sourceware.org \
    --cc=sebastian.huber@embedded-brains.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).