From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Kernel crash during queue create/destroy
Date: Wed, 15 Nov 2006 23:44:21 +0100 [thread overview]
Message-ID: <1163630662.4974.41.camel@domain.hid> (raw)
In-Reply-To: <1163629342.4974.36.camel@domain.hid>
On Wed, 2006-11-15 at 23:22 +0100, Philippe Gerum wrote:
> On Wed, 2006-11-15 at 22:01 +0100, Jan Kiszka wrote:
>
> > /me unfortunately failed to reproduce your problem here. Instead, I
> > found a regression in SVN head - different story for a different thread.
> >
>
> It's reproducible here. This bug triggers if you leave enough time
> between queue creation and deletion for Linux to deal with its usual
> business, like running workqueues... Additionally, this bug would not
> trigger with different queue names passed to the creation routines. It
> seems to be caused by out-of-sequence create/delete requests of /proc
> entries relayed to the proc_fs subsystem, which does not perform any
> sanity checks on the data it is submitted.
>
Mm, ok, got it. It's indeed an out-of-sequence issue. Will fix.
--
Philippe.
next prev parent reply other threads:[~2006-11-15 22:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 10:21 [Xenomai-help] Kernel crash during queue create/destroy Stephan Zimmermann
2006-11-15 13:19 ` Dmitry Adamushko
2006-11-15 14:44 ` Stephan Zimmermann
2006-11-15 21:01 ` Jan Kiszka
2006-11-15 22:22 ` Philippe Gerum
2006-11-15 22:36 ` Jan Kiszka
2006-11-15 22:43 ` Jan Kiszka
2006-11-15 22:46 ` Philippe Gerum
2006-11-15 22:52 ` Jan Kiszka
2006-11-15 22:44 ` Philippe Gerum [this message]
2006-11-16 11:57 ` Philippe Gerum
2006-11-16 12:59 ` Stephan Zimmermann
2006-11-16 13:26 ` Philippe Gerum
2006-11-16 15:35 ` Stephan Zimmermann
2006-11-16 15:44 ` Jan Kiszka
2006-11-17 12:38 ` Stephan Zimmermann
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=1163630662.4974.41.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=jan.kiszka@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.