All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai-core@domain.hid
Subject: [Xenomai-core] Racy pse51_mutex_check_init?
Date: Sat, 23 Aug 2008 10:33:03 +0200	[thread overview]
Message-ID: <48AFCB3F.6070902@domain.hid> (raw)

[-- Attachment #1: Type: text/plain, Size: 621 bytes --]

Hi Gilles,

trying to understand the cb_read/write lock usage, some question came up
here: What prevents that the mutexq iteration in pse51_mutex_check_init
races against pse51_mutex_destroy_internal?

If nothing, then I wonder if we actually have to iterate over the whole
queue to find out whether a given object has been initialized and
registered already or not. Can't this be encoded differently?

BTW, shadow_mutex.mutex is a kernel pointer sitting in a user-reachable
memory region? Why not using a handle here, like the native skin does?
Won't that allow to resolve the issue above as well?

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

             reply	other threads:[~2008-08-23  8:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-23  8:33 Jan Kiszka [this message]
2008-08-23 10:21 ` [Xenomai-core] Racy pse51_mutex_check_init? Gilles Chanteperdrix
2008-08-23 10:34   ` Gilles Chanteperdrix
2008-08-23 10:53   ` Philippe Gerum
2008-08-23 11:07     ` Gilles Chanteperdrix
2008-08-23 11:13       ` Philippe Gerum
2008-08-23 11:16       ` Philippe Gerum
2008-08-23 11:31         ` Gilles Chanteperdrix
2008-08-23 11:31       ` Jan Kiszka
2008-08-23 11:33         ` Gilles Chanteperdrix
2008-08-23 10:43 ` Gilles Chanteperdrix
2008-08-23 10:51   ` Jan Kiszka
2008-08-23 10:58     ` Gilles Chanteperdrix
2008-08-23 11:02       ` Gilles Chanteperdrix
2008-08-23 11:06         ` Jan Kiszka
2008-08-23 11:24           ` Gilles Chanteperdrix

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=48AFCB3F.6070902@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=Xenomai-core@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.