From: Jens Axboe <axboe@suse.de>
To: Felipe W Damasio <felipewd@terra.com.br>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] blk API update (and bug fix) to CDU535 cdrom driver
Date: Tue, 9 Sep 2003 21:55:49 +0200 [thread overview]
Message-ID: <20030909195549.GR4755@suse.de> (raw)
In-Reply-To: <3F5E12EC.6040502@terra.com.br>
On Tue, Sep 09 2003, Felipe W Damasio wrote:
> Hi Jens,
>
> Jens Axboe wrote:
> >held! Ugh, and the request function do_cdu535_request calls
> >schedule_timeout with the queue lock held (that is held when that
> >function is entered), that is very buggy as well. Should also use
> >set_current_state() right above that call, not open code it (that also
> >misses a memory barrier). Same function also has problems with request
> >handling. You should kill:
> >
> > if (!(req->flags & REQ_CMD))
> > continue; /* FIXME */
> >
> >that is very broken, make that:
> >
> > if (!blk_fs_request(req)) {
> > end_request(req, 0);
> > continue;
> > }
> >
> >and kill these two lines:
> >
> > if (rq_data_dir(req) != READ)
> > panic("Unknown SONY CD cmd");
> >
> >they are screwy too.
> >
> >Care to fix the things I outlined above?
>
> This patch I think fixes all these, doesn't it?
>
> It applies on top of my latest cli-sti-removal patch that I sent you.
That needed changes too, as per my last mail. Please send one complete
patch with all the fixes in, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2003-09-09 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F5DDEA8.6040901@terra.com.br>
[not found] ` <20030909143341.GA18257@suse.de>
[not found] ` <3F5DEA0D.6030701@terra.com.br>
[not found] ` <20030909153536.GH18257@suse.de>
2003-09-09 17:50 ` [PATCH] blk API update (and bug fix) to CDU535 cdrom driver Felipe W Damasio
2003-09-09 19:55 ` Jens Axboe [this message]
2003-09-09 20:21 ` Felipe W Damasio
2003-09-10 19:58 Matthew Wilcox
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=20030909195549.GR4755@suse.de \
--to=axboe@suse.de \
--cc=felipewd@terra.com.br \
--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 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.