From: Jens Axboe <axboe@suse.de>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IDE update for 2.6.7-rc3 [7/12]
Date: Fri, 11 Jun 2004 18:45:04 +0200 [thread overview]
Message-ID: <20040611164501.GA4309@suse.de> (raw)
In-Reply-To: <200406111759.54209.bzolnier@elka.pw.edu.pl>
On Fri, Jun 11 2004, Bartlomiej Zolnierkiewicz wrote:
>
> [PATCH] ide: fix ide-cd to not retry REQ_DRIVE_TASKFILE requests
>
> 'cat /proc/ide/hdx/identify' generates REQ_DRIVE_TASKFILE request
> (for WIN_PIDENTIFY command) even for devices controlled by ide-cd.
>
> All other drivers don't retry such requests.
>
> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>
>
> linux-2.6.7-rc3-bzolnier/drivers/ide/ide-cd.c | 2 +-
> 1 files changed, 1 insertion(+), 1 deletion(-)
>
> diff -puN drivers/ide/ide-cd.c~ide_cdrom_taskfile drivers/ide/ide-cd.c
> --- linux-2.6.7-rc3/drivers/ide/ide-cd.c~ide_cdrom_taskfile 2004-06-10 23:01:31.725338592 +0200
> +++ linux-2.6.7-rc3-bzolnier/drivers/ide/ide-cd.c 2004-06-10 23:01:31.731337680 +0200
> @@ -574,7 +574,7 @@ ide_startstop_t ide_cdrom_error (ide_dri
> if (drive == NULL || (rq = HWGROUP(drive)->rq) == NULL)
> return ide_stopped;
> /* retry only "normal" I/O: */
> - if (rq->flags & (REQ_DRIVE_CMD | REQ_DRIVE_TASK)) {
> + if (rq->flags & (REQ_DRIVE_CMD | REQ_DRIVE_TASK | REQ_DRIVE_TASKFILE)) {
> rq->errors = 1;
> ide_end_drive_cmd(drive, stat, err);
> return ide_stopped;
Was wondering whether it was clearer to use !blk_fs_request() instead,
but that would need looking at REQ_PC and REQ_BLOCK_PC. So for now the
above is fine with me, if you include ide_cdrom_abort() as well.
--
Jens Axboe
next prev parent reply other threads:[~2004-06-11 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 15:59 [PATCH] IDE update for 2.6.7-rc3 [7/12] Bartlomiej Zolnierkiewicz
2004-06-11 16:45 ` Jens Axboe [this message]
2004-06-11 17:55 ` 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=20040611164501.GA4309@suse.de \
--to=axboe@suse.de \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--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 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.