public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: unassigned@bugs.ecos.sourceware.org
Subject: [Bug 1001437] New: ADC HW drivers have race condition in cyg_io_set_config(CYG_IO_SET_CONFIG_ADC_[EN|DIS]ABLE)
Date: Mon, 02 Jan 2012 16:34:00 -0000	[thread overview]
Message-ID: <bug-1001437-777@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=1001437

           Summary: ADC HW drivers have race condition in
                    cyg_io_set_config(CYG_IO_SET_CONFIG_ADC_[EN|DIS]ABLE)
           Product: eCos
           Version: CVS
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: major
          Priority: low
         Component: ADC
        AssignedTo: unassigned@bugs.ecos.sourceware.org
        ReportedBy: bernard.fouche@kuantic.com
                CC: ecos-bugs@ecos.sourceware.org
             Class: Advice Request


Hello.

While looking at the source code of the LPC2XXX ADC driver, and after having
checked other ADC hardware drivers, it seems that all of these drivers, when
processing CYG_IO_SET_CONFIG_ADC_ENABLE and CYG_IO_SET_CONFIG_ADC_DISABLE, do
the following processing:

xxx_adc_disable(cyg_adc_channel *chan)
{
  xxx_adc_info *info=chan->device->dev_priv;

  ...

  info->chan_mask &= [some code to get bit value for concerned channel];
  ...
}

The opposite, for xxx_adc_enable(), is done with "info->chan_mask |= ..."

In multi-thread, if more than one thread handle ADC channels, since
info->chan_mask points, for all channels, to the same data area, then a thread
may be interrupted in the middle of the read-modify-write operation to update
the bit/channel field. Another thread can be scheduled and do its own
read-modify-write op on the same area.

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


             reply	other threads:[~2012-01-02 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-02 16:34 bugzilla-daemon [this message]
2012-01-02 16:35 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-1001437-777@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=unassigned@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).