All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Bultel <thierry.bultel@basystemes.fr>
To: xenomai@xenomai.org,
	Jean-Baptiste Tredez <jean-baptiste.tredez@basystemes.fr>
Subject: [Xenomai] crash in __pthread_mutex_check_init
Date: Tue, 26 Apr 2016 16:15:26 +0200	[thread overview]
Message-ID: <571F77FE.2040100@basystemes.fr> (raw)

Hi,

I am currently still porting ipipe to kernel 4.5, and after having 
solved some issues
(for instance, I found out that the DTB are no longer compatible, 
between 3.18.12 and 4.5
and without recompiling the device tree, the hardware address of the 
timer is wrong, preventing the tsc to work,
and making the kernel lockup on whatever sleep call )

... I wanted to pass the regression tests and I am now facing this one:
The posix "leaks" test leads to a kernel crash

Apparently, the shadow mutex address returned by _xn_safe_copy_from_user 
is wrong, and the crash occurs when
accessing umx->shadow_mutex.magic

I can consider that the problem I have is obviously in my ipipe work, 
because the same xenomai version works fine
with 3.18.12 ...
But I do not see any relation for now.

I have some questions, please:
1) What is the meaning of CONFIG_XENO_FASTSYNCH ? I see that the 
_pthread_mutex_check_init syscall only exists
when CONFIG_XENO_FASTSYNC is defined (which is the case, here)

2) I have a number of regression tests that pass, proving that the 
syscall interface is not so completely broken,
where should I pay more attention in the ipipe side, in my case ?

Thanks
Thierry

                 reply	other threads:[~2016-04-26 14:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=571F77FE.2040100@basystemes.fr \
    --to=thierry.bultel@basystemes.fr \
    --cc=jean-baptiste.tredez@basystemes.fr \
    --cc=xenomai@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.