From: "Corrin Meyer" <cjmeyer@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Question about Unlock
Date: Tue, 02 Dec 2008 15:22:00 -0000 [thread overview]
Message-ID: <c3161b780812020702g30ce7ae4i34b6d323fcaa0624@mail.gmail.com> (raw)
Looking at the unlock_inner method it would seem that it is possible
for calls to unlock_inner to nest. Since the lock is set (possibly)
to 0 before the unlock_inner function returns it is possible for
another interrupt to occur forcing another call to unlock_inner to
execute on the thread stack again. If the posted DSRs do not force a
context switch the calls to unlock_inner are nested on the current
running stack. Given the correct timing it seems possible that nested
unlock_inner methods could result in a stack overflow.
I just wanted to make sure that my understanding is correct: it is
possible for 'continuous' interrupts to result in a Task stack
overflow (which may or may not also result in an interrupt stack
overflow depending on the stack sizes) meaning even if I have an
interrupt stack to run the interrupts and DSRs on the Task stack sizes
still need to accommodate some amount nesting interrupt/DSR overhead.
~ Corrin
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2008-12-02 15:03 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=c3161b780812020702g30ce7ae4i34b6d323fcaa0624@mail.gmail.com \
--to=cjmeyer@gmail.com \
--cc=ecos-discuss@ecos.sourceware.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 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).