All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Andre Hedrick <andre@linuxdiskcert.org>
Cc: Andrew Morton <akpm@zip.com.au>,
	lkml <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: block completion races
Date: Wed, 16 Jan 2002 08:09:48 +0100	[thread overview]
Message-ID: <20020116080948.G3805@suse.de> (raw)
In-Reply-To: <3C44DC7B.D960D15D@zip.com.au> <Pine.LNX.4.10.10201152001400.26467-100000@master.linux-ide.org>
In-Reply-To: <Pine.LNX.4.10.10201152001400.26467-100000@master.linux-ide.org>

On Tue, Jan 15 2002, Andre Hedrick wrote:
> 
> We have a more interesting problem!
> This does not show up in 2.5.1 which is patch base for 2.5.3-pre1.
> It does show up in 2.5.2-pre10 but I have not walked the patch through
> 2.5.2preX series.
> 
> We have a very bad queue race that is PIO specific but really the whole
> darn driver before the patch was applied.  ACB only tighten the driver's
> alignment to the NCITS standards.  One should note the direct access via
> the ioctl does not lock the driver.  Only coming down from BLOCK will this
> event occur.
> 
> Repeatable test "hdparm -d0 -t /dev/hdx"
> 
> If you apply the acb-io patch to 2.5.1 this does not happen.
> 
> In the introduction of BIO, there were no "q->queue_lock" applied to
> protecting the queue.
> 
>         /*
>          * Is meant to protect the queue in the future instead of
>          * io_request_lock
>          */
>         spinlock_t              queue_lock;
> 
> Well we pulled "io_request_lock" but did we forgot to insert or add
> q->queue_lock spinlocks?
> 
> It is going to be a LONG LONG NIGHT :-(

ide_lock == q->queue_lock

ide-probe.c:ide_init_queue():	blk_init_queue(q, do_ide_request, &ide_lock);

-- 
Jens Axboe


  reply	other threads:[~2002-01-16  7:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-16  1:50 block completion races Andrew Morton
2002-01-16  4:11 ` Andre Hedrick
2002-01-16  7:09   ` Jens Axboe [this message]
2002-01-16  7:07 ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2002-01-16 16:55 Manfred Spraul
2002-01-16 18:50 ` Jens Axboe

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=20020116080948.G3805@suse.de \
    --to=axboe@suse.de \
    --cc=akpm@zip.com.au \
    --cc=andre@linuxdiskcert.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.