linux-kernel - Re: ext3 directory corruption under Xen

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]

Date:	Mon, 23 Jun 2008 12:13:47 -0700
From:	"adam radford" <aradford@...il.com>
To:	"Christopher S. Aker" <caker@...shore.net>
Cc:	linux-kernel@...r.kernel.org,
	"xen devel" <xen-devel@...ts.xensource.com>
Subject: Re: ext3 directory corruption under Xen

On Mon, Jun 23, 2008 at 9:15 AM, Christopher S. Aker <caker@...shore.net> wrote:

> It's happened on a number of different hosts, all of the same hardware and
> software configuration (Xen 3.2 64bit, 32bit pae dom0, 32bit pae domUs.  LVM
> backend with 3ware hardware RAID-1).

Do you have Intel EM64T and the older 3w-xxxx driver with 4GB+ RAM?
If so there is a driver patch for older kernels to fix an issue where the driver
was over-riding the default DMA direction with DMA_BIDIRECTIONAL,
and this caused corruption going through the SWIOTLB code (not IOMMU
w/AMD).

A driver patch for older kernels including XenServer-4.1 is available here:

http://www.3ware.com/KB/article.aspx?id=15243&cNode=6I1C6S

This doesn't explain however your failures with 2.6.24 2.6.25, etc, since
this issue is no longer valid after the scsi_dma_map() changes that went
into most scsi drivers since 2.6.23.

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