Return-Path: <linux-kernel-owner+w=401wt.eu-S932189AbYCGUh7@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932189AbYCGUh7 (ORCPT <rfc822;w@1wt.eu>);
	Fri, 7 Mar 2008 15:37:59 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1762962AbYCGUhq
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Fri, 7 Mar 2008 15:37:46 -0500
Received: from fg-out-1718.google.com ([72.14.220.152]:63921 "EHLO
	fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1761544AbYCGUho (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 7 Mar 2008 15:37:44 -0500
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id;
        b=CWvlAYOSEOJROM7op2IqQCUaJSvMDut4/ZG1F9qKM6RlhY6i4Rs/peTLc5Li3lYb28qGYJC1tvwp9WnRaLB9n3yG9aPIoiq2K5q+3SErqhxWkHq8KPQwjGDgHMn+evBXpA2PU8gt1+gJHQWf2o4eabxdy5wVX4pX/Zt/120pgMw=
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: petkovbb@gmail.com
Subject: Re: Commit 9f10d9ee breaks CD mounting/burning
Date: Fri, 7 Mar 2008 21:39:43 +0100
User-Agent: KMail/1.9.9
Cc: walt <w41ter@gmail.com>, linux-ide@vger.kernel.org,
       linux-kernel@vger.kernel.org
References: <200803062235.00396.bzolnier@gmail.com> <20080307054825.GA19778@gollum.tnic>
In-Reply-To: <20080307054825.GA19778@gollum.tnic>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200803072139.43167.bzolnier@gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 4521
Lines: 114

On Friday 07 March 2008, Borislav Petkov wrote:
> 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@gmail.com>
> > > 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@gmail.com>
> > 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@gmail.com>
> > > 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@gmail.com>
> > Cc: Borislav Petkov <petkovbb@googlemail.com>
> > Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> > ---
> >  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?

Yep.

Thanks for checking it, I'll push the patch to Linus.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/