From: Jens Axboe <axboe@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH (for comment): ide-cd possible race in PIO mode
Date: Wed, 17 Nov 2004 16:37:07 +0100 [thread overview]
Message-ID: <20041117153706.GH26240@suse.de> (raw)
In-Reply-To: <1100697589.32677.3.camel@localhost.localdomain>
On Wed, Nov 17 2004, Alan Cox wrote:
> Working on tracing down Fedora bug #115458
> (https://bugzilla.redhat.com/bugzilla/process_bug.cgi) I found what
> appears to be a race between the IDE CD driver and the hardware status.
> It doesn't appear to explain the bug at all but it does look like a bug
> of itself
>
> When we issue an ide command the status bits don't become valid for
> 400nS. In the DMA case ide_execute_command handles this but in the PIO
> case we don't do the needed locking, use OUTBSYNC to avoid posting or
> delay. This means that in some situations we can execute the command
> handler in PIO mode before the command status bits are valid and the
> handler may read and act wrongly.
>
> --- drivers/ide/ide-cd.c~ 2004-11-17 14:08:42.950485320 +0000
> +++ drivers/ide/ide-cd.c 2004-11-17 14:08:42.951485168 +0000
> @@ -897,7 +897,10 @@
> return ide_started;
> } else {
> /* packet command */
> - HWIF(drive)->OUTB(WIN_PACKETCMD, IDE_COMMAND_REG);
> + spin_lock_irqsave(&ide_lock, flags);
> + HWIF(drive)->OUTBSYNC(WIN_PACKETCMD, IDE_COMMAND_REG);
> + ndelay(400);
> + spin_unlock_irqsave(&ide_lock, flags);
> return (*handler) (drive);
> }
> }
What good does the lock do?
--
Jens Axboe
next prev parent reply other threads:[~2004-11-17 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 13:19 PATCH (for comment): ide-cd possible race in PIO mode Alan Cox
2004-11-17 15:37 ` Jens Axboe [this message]
2004-11-17 16:25 ` Alan Cox
2004-11-17 20:56 ` Jens Axboe
2004-11-22 7:58 ` Jens Axboe
2004-11-24 11:35 ` Alan Cox
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=20041117153706.GH26240@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).