linux-kernel - Re: unchecked_isa_dma and BusLogic SCSI controller

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20061101173358.7b027d13.randy.dunlap@oracle.com>
Date:	Wed, 1 Nov 2006 17:33:58 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Jun Sun <jsun@...sun.net>
Cc:	linux-scsi@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>
Subject: Re: unchecked_isa_dma and BusLogic SCSI controller

On Wed, 1 Nov 2006 15:53:30 -0800 Jun Sun wrote:

> 
> Can someone enlighten me on what "unchecked_isa_dma" means in the
> struct scsi_host_template?

It's documented in Documentation/scsi/scsi_mid_low_api.txt:

    unchecked_isa_dma - 1=>only use bottom 16 MB of ram (ISA DMA addressing
                   restriction), 0=>can use full 32 bit (or better) DMA
                   address space

> Specifically why Bus_Logic_template has
> it set to 1?

maybe ask on linux-scsi@...r.kernel.org (cc-ed)

> I am trying to reserve a block of memory (>16MB) starting from 0 and hide
> it from kernel.  As a result, the DMA zone becomes 0 in size.
> 
> Because Bus_Logic_template has unchecked_isa_dma set to 1, the driver
> will attempt to allocate a block of memory from DMA zone and thus
> causes OOMs during its initialization.
> 
> It is hard for me to see why BusLogic controller would only do DMA
> in low 16MB.  Is there a fix for this?

Does anyone know that controller hardware and its limitations?

If the driver can't handle highmem addresses, you could just change
it so that
(a) it does not set unchecked_isa_dma
(b) it sets .slave_alloc in the host template and then does
like the <slave_alloc> function in ppa.c or imm.c:
call blk_queue_bounce_limit() to set an address for which bounce
buffers (from highmem to lowmem) will be used.
[I don't guarantee that to work for BusLogic.]

> BTW, I also tried to increase MAX_DMA_ADDRESS to cover the whole memory
> area.  While the OOMs are gone during BusLogic driver initialization, 
> kernel fails to find labelled root partition or fail to open
> the initial console.  It appears the disk (or the scsi) is not working
> properly after increasing MAX_DMA_ADDRESS.
> 
> My platform is vmplayer.  Pretty cool for devel.
> 
> Cheers.
> 
> Jun

---
~Randy
-
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/