Re: Commit 9f10d9ee breaks CD mounting/burning

[Borislav Petkov]

On Thu, Mar 06, 2008 at 10:35:00PM +0100, Bartlomiej Zolnierkiewicz wrote:
> 
> On Thursday 06 March 2008, walt wrote:
> > Hi Bartolmiej,
> > 
> > For me, this commit causes the problem it's intended to fix:
> > 
> > commit 9f10d9ee0ac6d79d7bc8b9a158bf4a29322d84d3
> > Author: Bartlomiej Zolnierkiewicz <bzolnier@xxxxxxxxx>
> > Date:   Tue Feb 26 21:50:35 2008 +0100
> > 
> >      ide-cd: fix 'ireason' handling for REQ_TYPE_ATA_PC requests
> > 
> >      This fixes some hangs caused by not finishing the transfer before ending
> >      the request and also makes use of 'ireason == 1' quirk for spurious IRQs.
> > 
> > When I mount a CD there is a long delay, and I see this error message:
> > 
> > hdc: ide_cd_check_ireason: wrong transfer direction!
> > cdrom: failed setting lba address space
> > hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> > ide: failed opcode was: unknown
> > hdc: drive not ready for command
> > <repeated many times>
> > 
> > When I revert this commit everything works properly again, including
> > CD burning.
> > 
> > Here is the drive info:
> > 
> > hdc: TSSTcorpCD/DVDW SH-S182M, ATAPI CD/DVD-ROM drive
> > hdc: host max PIO5 wanted PIO255(auto-tune) selected PIO4
> > hdc: UDMA/33 mode selected
> > hdc: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache
> > Uniform CD-ROM driver Revision: 3.20
> > hdc: UDMA/33 mode selected
> > 
> > I'm happy to try patches or supply more info, just let me know
> > what you need.
> 
> Does the following patch help?
> 
> [ Borislav, please take a look and double check that it is OK. ]
> 
> From: Bartlomiej Zolnierkiewicz <bzolnier@xxxxxxxxx>
> Subject: [PATCH] ide-cd: mark REQ_TYPE_ATA_PC write requests with REQ_RW flag
> 
> On Thursday 06 March 2008, walt wrote:
> 
> > For me, this commit causes the problem it's intended to fix:
> > 
> > commit 9f10d9ee0ac6d79d7bc8b9a158bf4a29322d84d3
> > Author: Bartlomiej Zolnierkiewicz <bzolnier@xxxxxxxxx>
> > Date:   Tue Feb 26 21:50:35 2008 +0100
> > 
> >      ide-cd: fix 'ireason' handling for REQ_TYPE_ATA_PC requests
> > 
> >      This fixes some hangs caused by not finishing the transfer before ending
> >      the request and also makes use of 'ireason == 1' quirk for spurious IRQs.
> > 
> > When I mount a CD there is a long delay, and I see this error message:
> > 
> > hdc: ide_cd_check_ireason: wrong transfer direction!
> > cdrom: failed setting lba address space
> > hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> > ide: failed opcode was: unknown
> > hdc: drive not ready for command
> > <repeated many times>
> > 
> > When I revert this commit everything works properly again, including
> > CD burning.
> 
> It turned out that REQ_TYPE_ATA_PC write requests were not marked as such
> (the previous commit assumed them to be).
> 
> Reported-by: walt <w41ter@xxxxxxxxx>
> Cc: Borislav Petkov <petkovbb@xxxxxxxxxxxxxx>
> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@xxxxxxxxx>
> ---
>  drivers/ide/ide-cd_ioctl.c |    4 ++++
>  1 file changed, 4 insertions(+)
> 
> Index: b/drivers/ide/ide-cd_ioctl.c
> ===================================================================
> --- a/drivers/ide/ide-cd_ioctl.c
> +++ b/drivers/ide/ide-cd_ioctl.c
> @@ -457,6 +457,10 @@ int ide_cdrom_packet(struct cdrom_device
>  	   layer. the packet must be complete, as we do not
>  	   touch it at all. */
>  	ide_cd_init_rq(drive, &req);
> +
> +	if (cgc->data_direction == CGC_DATA_WRITE)
> +		req.cmd_flags |= REQ_RW;
> +
>  	memcpy(req.cmd, cgc->cmd, CDROM_PACKET_SIZE);
>  	if (cgc->sense)
>  		memset(cgc->sense, 0, sizeof(struct request_sense));

Here's how i understand it (and correct me if i'm wrong):

req.cmd_flags & 0x1 (i.e. the least sig. bit) was remaining unset for write requests
and that's why the ireason check in the interrupt handler was failing loudly.
This sets it correctly so that rq_data_dir(rq) evaluates to the correct data
direction of the request, no?

-- 
Regards/Gruß,
    Boris.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/