All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Steven Seeger <steven.seeger@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] rt_queue_write return 1, with no receiver
Date: Wed, 11 Mar 2009 18:36:38 +0100	[thread overview]
Message-ID: <49B7F6A6.5060603@domain.hid> (raw)
In-Reply-To: <494CC2B0-5509-46F5-B480-CA34038F0226@domain.hid>

Steven Seeger wrote:
> On Mar 11, 2009, at 1:15 PM, Philippe Gerum wrote:
> 
>> Then I have no clue; you may want to try simplifying your test until 
>> the bug disappears.
> 
> I also suggested this already. :)
> 
> We are also always writing the same structure. It is statically 
> allocated and we use queues as a means of providing a series of snapshots.
> 
> Our app is entirely userspace. Could memory corruption in userspace 
> cause issues with the /proc entry?
>

You are sharing buffers with kernel space using RT_QUEUEs. If anything goes 
wrong writing to this address space, you may well end up corrupting some kernel 
data, including some internal Xenomai data structures. The fact that looking at 
/proc/xenomai crashes the system is telling, since the backing code may attempt 
to scan such data structures.

Since you also have your own driver running, this might be another source for 
the issue. Non-reg tests did not reveal any issue with RT_QUEUEs so far.

> Steven
> 
> 


-- 
Philippe.


  reply	other threads:[~2009-03-11 17:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10  0:27 [Xenomai-help] rt_queue_write return 1, with no receiver Mark Saiia
2009-03-10  9:37 ` Philippe Gerum
2009-03-10 18:21   ` Steven Seeger
2009-03-10 18:57   ` Steven Seeger
2009-03-10 19:56     ` Philippe Gerum
     [not found]       ` <67b6b3430903101403r183d6d4cwe100619a293abae2@domain.hid>
2009-03-10 21:07         ` Philippe Gerum
2009-03-10 22:16           ` Mark Saiia
2009-03-10 22:24             ` Philippe Gerum
     [not found]               ` <67b6b3430903101552u37244233s587898c4d0f9ef3d@domain.hid>
2009-03-11  9:14                 ` Philippe Gerum
     [not found]                   ` <67b6b3430903110951m71679f89ud83859654f04aabb@domain.hid>
2009-03-11 17:04                     ` Philippe Gerum
2009-03-11 17:07                       ` Steven Seeger
2009-03-11 17:15                         ` Philippe Gerum
2009-03-11 17:18                           ` Steven Seeger
2009-03-11 17:36                             ` Philippe Gerum [this message]
2009-03-11 17:38                               ` Steven Seeger
2009-03-11 17:39                               ` Steven Seeger
     [not found]                               ` <67b6b3430903111043s628c5c64m89cc8c726bdf6ff9@domain.hid>
2009-03-11 17:45                                 ` [Xenomai-help] Fwd: " Mark Saiia
2009-03-11 17:17                       ` [Xenomai-help] " Jan Kiszka

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=49B7F6A6.5060603@domain.hid \
    --to=rpm@xenomai.org \
    --cc=steven.seeger@domain.hid \
    --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.