linux-kernel - Calgary and bad_dma

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-next>] [day] [month] [year] [list]

Message-Id: <20080909211941.0a0fda6a.zaitcev@redhat.com>
Date:	Tue, 9 Sep 2008 21:19:41 -0600
From:	Pete Zaitcev <zaitcev@...hat.com>
To:	<jdmason@...zu.us>, <muli@...ibm.com>
Cc:	zaitcev@...hat.com, linux-kernel@...r.kernel.org
Subject: Calgary and bad_dma_address

Hi, guys:

I was reading arch/x86/kernel/pci-calgary_64.c today, and noticed that
apparently nothing prevents iommu_area_alloc from returning a zero.
But bad_dma_address is zero too. Doesn't it concern anyone?
If the first allocation asks for a page-aligned buffer to be mapped,
a spurious bad address will result, if I understand this right.

The simplest way to avoid the problem is to lose a page and set a bit
in tce_table_setparms():
   set_bit(tbl->it_map, bad_dma_address);
But I don't see anything like that done anywhere.

-- Pete
--
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/