From: Alan Cox <alan@redhat.com>
To: Ken Ashcraft <kash@stanford.edu>
Cc: linux-kernel@vger.kernel.org, alan@redhat.com, mc@cs.stanford.edu
Subject: Re: [CHECKER] Race condition in i2o_core.c
Date: Fri, 2 Apr 2004 04:19:11 -0500 [thread overview]
Message-ID: <20040402091911.GB22652@devserv.devel.redhat.com> (raw)
In-Reply-To: <5.2.1.1.2.20040401172809.01bcfa50@kash.pobox.stanford.edu>
On Thu, Apr 01, 2004 at 05:46:00PM -0800, Ken Ashcraft wrote:
> Looks like there is a race condition in i2o_core_reply involving the
> variable "evt_in". Notice that the increment of evt_in is protected by the
> lock, but the reads are not protected. It looks like "events" should also
> be protected by the lock. If this is not a race condition, the increment
> should not be inside the critical section.
>
> Feedback is appreciated.
Looks a fair catch to me.
prev parent reply other threads:[~2004-04-02 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 1:46 [CHECKER] Race condition in i2o_core.c Ken Ashcraft
2004-04-02 2:08 ` Randy.Dunlap
2004-04-02 9:19 ` Alan Cox [this message]
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=20040402091911.GB22652@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=kash@stanford.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mc@cs.stanford.edu \
/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