netdev - Re: [PATCH 3/20][BNX2]: Add 40-bit DMA workaround for 5708.

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: <1178130232.4820.62.camel@dell>
Date:	Wed, 02 May 2007 11:23:52 -0700
From:	"Michael Chan" <mchan@...adcom.com>
To:	"Jeff Garzik" <jeff@...zik.org>
cc:	"David Miller" <davem@...emloft.net>,
	"netdev" <netdev@...r.kernel.org>
Subject: Re: [PATCH 3/20][BNX2]: Add 40-bit DMA workaround for 5708.

On Wed, 2007-05-02 at 11:29 -0400, Jeff Garzik wrote:
> Michael Chan wrote:
> > A non-IOMMU system using 64-bit dma_addr_t will always set
> > CONFIG_HIGHMEM, right?
> 
> No.
> 
May be I misunderstood the code in illegal_highdma() in net/core/dev.c
where it is checking to see if it needs to linearize the SKB when the
device does not support 64-bit DMA.  I'm using similar assumptions for
the 40-bit address check in the patch.

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html