public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001679] New: Cyg_Counter::add_alarm() can trash list w/ immediate triggers
Date: Fri, 28 Sep 2012 17:03:00 -0000	[thread overview]
Message-ID: <bug-1001679-13@http.bugs.ecos.sourceware.org/> (raw)

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001679

           Summary: Cyg_Counter::add_alarm() can trash list w/ immediate
                    triggers
           Product: eCos
           Version: 3.0
          Platform: All
        OS/Version: Other
            Status: UNCONFIRMED
          Severity: normal
          Priority: low
         Component: Kernel
        AssignedTo: unassigned@bugs.ecos.sourceware.org
        ReportedBy: meerjulien@gmail.com
                CC: ecos-bugs@ecos.sourceware.org
             Class: Advice Request


Created an attachment (id=1946)
 --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1946)
Failing test case

When calling cyg_alarm_initialize with a trigger time in the past,
Cyg_Counter::add_alarm will first mark the alarm (A) as enabled before
dispatching it (B) & finally marking it as disabled (C).

Also Cyg_Counter::initialize will call rem_alarm if an alarm is enabled (D).

Hence a sequence where a callback re-enables the triggered alarm can result in
trashing the alarm list.

[begin snippet]
void Cyg_Counter::add_alarm( Cyg_Alarm *alarm )
{
    alarm->enabled = true;                     // A

    if( alarm->trigger <= counter )
    {
        alarm->alarm(alarm, alarm->data);      // B

        if( alarm->interval != 0 && alarm->enabled )
        {
            alarm->trigger += alarm->interval;
            alarm->synchronize();
        }
        else
        {
            alarm->enabled = false;            // C
            return;
        }
[end snippet]

[begin snippet]
void Cyg_Alarm::initialize(                
    cyg_tick_count    t,                // Absolute trigger time
    cyg_tick_count    i                 // Relative retrigger interval
    )
{
    Cyg_Scheduler::lock();
    if( enabled ) counter->rem_alarm(this);   // D
[end snippet]

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-09-28 17:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-28 17:03 bugzilla-daemon [this message]
2012-09-28 17:06 ` [Bug 1001679] " bugzilla-daemon
2012-09-28 17:03 [Bug 1001679] New: " bugzilla-daemon

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=bug-1001679-13@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-bugs@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).