linux-kernel - Re: ISP1760 driver crashes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.0811191131320.2418-100000@iolanthe.rowland.org>
Date:	Wed, 19 Nov 2008 11:33:50 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Jens Axboe <jens.axboe@...cle.com>
cc:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
	"Hommel, Thomas (GE EntSol, Intelligent Platforms)" 
	<Thomas.Hommel@...anuc.com>, USB list <linux-usb@...r.kernel.org>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: ISP1760 driver crashes

On Wed, 19 Nov 2008, Jens Axboe wrote:

> > --- usb-2.6.orig/drivers/scsi/scsi_lib.c
> > +++ usb-2.6/drivers/scsi/scsi_lib.c
> > @@ -1684,7 +1684,7 @@ static void scsi_request_fn(struct reque
> >  u64 scsi_calculate_bounce_limit(struct Scsi_Host *shost)
> >  {
> >  	struct device *host_dev;
> > -	u64 bounce_limit = 0xffffffff;
> > +	u64 bounce_limit = BLK_BOUNCE_HIGH;
> >  
> >  	if (shost->unchecked_isa_dma)
> >  		return BLK_BOUNCE_ISA;
> > 
> 
> The best solution is probably to either provide a "doesn't do highmem"
> in the scsi host template, or provide an appropriate DMA mask for the
> pci device to indicate it through that setting instead.

The DMA mask is currently set to NULL.  Is that not appropriate for a 
device that can't do DMA?  If not, then what would be appropriate?

Also, is the patch above not correct?

Alan Stern

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