linux-kernel - iommu bug

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

Message-ID: <20090616114410.GE3735@think>
Date:	Tue, 16 Jun 2009 07:44:10 -0400
From:	Chris Mason <chris.mason@...cle.com>
To:	David Woodhouse <david.woodhouse@...el.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: iommu bug

Hello,

I posted this one a while ago (last September) and it disappeared on me.
I've recently turned the iommu back on and its back:

Last time David asked me to try with iommu=strict, which I'll do when
back from vacation.  At the time we thought the bug was an IO being
submitted with the same page on two different bios.  For whatever
reason, btrfs raid1 and raid10 hit this harder than MD.

This oops is 2.6.30 + the btrfs tree (which doesn't change iommu at
all).

kernel BUG at drivers/pci/intel-iommu.c:1524!
invalid opcode: 0000 [#1] SMP
last sysfs file: /sys/block/loop3/removable
CPU 1
Modules linked in: loop btrfs netconsole configfs 3w_9xxx
Pid: 30595, comm: btrfs-worker-5 Not tainted 2.6.30 #6
RIP: 0010:[<ffffffff803ee688>]  [<ffffffff803ee688>] domain_page_mapping+0xa4/0xf7
RSP: 0018:ffff880004cc5af0  EFLAGS: 00010006
RAX: ffff880110e96e00 RBX: ffff88014eda3f40 RCX: 00000000a958e001
RDX: ffff880110e96000 RSI: 0000000000000006 RDI: ffff88014eda3f88
RBP: ffff880004cc5b30 R08: 0000000000000027 R09: 0000000000001000
R10: 0000000000000000 R11: 0000000000000002 R12: 000000000006ec4a
R13: 000000000006ec4b R14: 000000000006ec4a R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff880004c62000(0000) knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 00007f0de3efe508 CR3: 0000000000201000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process btrfs-worker-5 (pid: 30595, threadinfo ffff8801339e6000, task ffff8801085b2280)
Stack:
 0000000000000001 00000000affc0000 0000000000000018 ffff88014eda3f40
 ffff88011d826000 0000000000000018 00000000affc0000 0000000000000000
 ffff880004cc5bb0 ffffffff803efb31 ffff8800572fe080 0000000000000000
Call Trace:
Code: 48 63 f6 48 89 df 48 c1 e6 0c 48 03 75 c8 e8 dd fd ff ff 48 85 c0 75 07 b8 f4 ff ff ff eb 50 48 8b 08 48 f7 c1 00 f0 ff ff 74 04 <0f> 0b eb fe 4c 89 e2 48 c1 e2 0c 48 09 ca 48 83 e2 fc 48 0b 55
RIP  [<ffffffff803ee688>] domain_page_mapping+0xa4/0xf7
 RSP <ffff880004cc5af0>
---[ end trace e1cd0e6624485448 ]---
--
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/