From: Jens Axboe <axboe@suse.de>
To: martin@dalecki.de
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
linux-kernel@vger.kernel.org
Subject: Re: please DON'T run 2.5.27 with IDE!
Date: Wed, 24 Jul 2002 13:53:22 +0200 [thread overview]
Message-ID: <20020724115322.GC5159@suse.de> (raw)
In-Reply-To: <3D3E90E4.3080108@evision.ag>
On Wed, Jul 24 2002, Marcin Dalecki wrote:
> >>So look at drivers which call blk_start_queue() from within
> >>q->request_fn context, which is, well, causing deliberate *recursion*.
> >>
> >
> >
> >Are you sure? If so they should first check whether queue is
> >started/stopped, if they don't it is a bug.
>
> void blk_start_queue(request_queue_t *q)
> {
> if (test_bit(QUEUE_FLAG_STOPPED, &q->queue_flags)) {
> unsigned long flags;
>
> ================== possigle race here for qeue_flags BTW.
>
> spin_lock_irqsave(q->queue_lock, flags);
> clear_bit(QUEUE_FLAG_STOPPED, &q->queue_flags);
>
> if (!elv_queue_empty(q))
> q->request_fn(q);
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> If we call it from within request_fn then if this isn't recursion on the
> kernel stack then I don't know...
>
> spin_unlock_irqrestore(q->queue_lock, flags);
> }
> }
Care to enlighten us on exactly which block drivers call
blk_start_queue() from request_fn?
--
Jens Axboe
next prev parent reply other threads:[~2002-07-24 11:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 19:37 please DON'T run 2.5.27 with IDE! Bartlomiej Zolnierkiewicz
2002-07-22 20:39 ` Andries Brouwer
2002-07-22 23:25 ` Thunder from the hill
2002-07-23 0:39 ` A Guy Called Tyketto
2002-07-23 0:58 ` Thunder from the hill
2002-07-23 1:10 ` Bartlomiej Zolnierkiewicz
2002-07-23 8:03 ` Morten Helgesen
2002-07-23 12:47 ` Bartlomiej Zolnierkiewicz
2002-07-23 13:00 ` Marcin Dalecki
2002-07-23 13:42 ` Bartlomiej Zolnierkiewicz
2002-07-23 13:58 ` Marcin Dalecki
2002-07-23 19:52 ` Jan Harkes
2002-07-23 20:08 ` Andre Hedrick
2002-07-24 10:24 ` Marcin Dalecki
2002-07-23 20:24 ` Bartlomiej Zolnierkiewicz
2002-07-24 10:30 ` Marcin Dalecki
2002-07-24 10:54 ` Bartlomiej Zolnierkiewicz
2002-07-24 11:35 ` Marcin Dalecki
2002-07-24 11:53 ` Jens Axboe [this message]
2002-07-24 12:08 ` Marcin Dalecki
2002-07-24 12:39 ` Bartlomiej Zolnierkiewicz
2002-07-24 12:41 ` Jens Axboe
2002-07-24 12:49 ` Bartlomiej Zolnierkiewicz
2002-07-24 12:50 ` Jens Axboe
2002-07-24 13:08 ` Marcin Dalecki
2002-07-24 13:25 ` Jens Axboe
2002-07-24 13:35 ` Bartlomiej Zolnierkiewicz
2002-07-24 13:36 ` Jens Axboe
2002-07-24 13:38 ` Marcin Dalecki
2002-07-24 13:35 ` Marcin Dalecki
2002-07-24 12:43 ` Bartlomiej Zolnierkiewicz
2002-07-24 13:10 ` Marcin Dalecki
2002-07-24 13:21 ` Bartlomiej Zolnierkiewicz
-- strict thread matches above, loose matches on Subject: below --
2002-07-22 19:43 Petr Vandrovec
2002-07-22 19:46 ` Bartlomiej Zolnierkiewicz
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=20020724115322.GC5159@suse.de \
--to=axboe@suse.de \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
/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