From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Tomáš Janoušek" <tomi@nomi.cz>
Cc: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>,
Stanislaw Gruszka <sgruszka@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn: memory corruption with WPA enterprise
Date: Thu, 10 Nov 2011 11:02:04 -0600 [thread overview]
Message-ID: <4EBC038C.1050700@lwfinger.net> (raw)
In-Reply-To: <20111110164230.GB24533@nomi.cz>
On 11/10/2011 10:42 AM, Tomáš Janoušek wrote:
> (Don't be scared by the vboxdrv messages. Those modules don't compile with
> 3.2-rc1, and the bug happens there as well.)
The following patch will fix the 3.2-rc1 build problem.
Index: vboxhost/vboxpci/linux/VBoxPci-linux.c
===================================================================
--- vboxhost.orig/vboxpci/linux/VBoxPci-linux.c
+++ vboxhost/vboxpci/linux/VBoxPci-linux.c
@@ -146,7 +146,11 @@ static int __init VBoxPciLinuxInit(void)
#endif
#ifdef VBOX_WITH_IOMMU
+# if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 2, 0)
+ if (iommu_present(&pci_bus_type))
+#else
if (iommu_found())
+#endif
printk(KERN_INFO "vboxpci: IOMMU found\n");
else
printk(KERN_INFO "vboxpci: IOMMU not found (not registered)\n");
@@ -984,9 +988,15 @@ int vboxPciOsInitVm(PVBOXRAWPCIDRVVM pT
printk(KERN_DEBUG "vboxPciOsInitVm: %p\n", pThis);
#endif
#ifdef VBOX_WITH_IOMMU
+# if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 2, 0)
+ if (iommu_present(&pci_bus_type))
+ {
+ pThis->pIommuDomain = iommu_domain_alloc(&pci_bus_type);
+#else
if (iommu_found())
{
pThis->pIommuDomain = iommu_domain_alloc();
+#endif
if (!pThis->pIommuDomain)
{
printk(KERN_DEBUG "cannot allocate IOMMU domain\n");
next prev parent reply other threads:[~2011-11-10 17:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 17:15 Tomáš Janoušek
2011-10-31 16:03 ` Stanislaw Gruszka
2011-11-09 15:54 ` Tomáš Janoušek
2011-11-09 15:59 ` wwguy
2011-11-09 16:51 ` Stanislaw Gruszka
2011-11-10 9:18 ` Tomáš Janoušek
2011-11-10 11:47 ` Stanislaw Gruszka
2011-11-10 12:53 ` Tomáš Janoušek
2011-11-10 16:07 ` Stanislaw Gruszka
2011-11-10 15:24 ` Guy, Wey-Yi
2011-11-10 16:42 ` Tomáš Janoušek
2011-11-10 17:02 ` Larry Finger [this message]
2011-11-10 16:30 ` Tomáš Janoušek
2011-11-11 5:47 ` Stanislaw Gruszka
2011-11-11 15:01 ` Tomáš Janoušek
2011-11-14 14:07 ` Stanislaw Gruszka
2011-11-19 18:11 ` Tomáš Janoušek
2011-11-20 2:13 ` wwguy
2011-11-20 3:20 ` Tomáš Janoušek
2011-11-20 4:28 ` wwguy
2011-11-20 20:40 ` Tomáš Janoušek
2012-02-10 18:09 ` Tomáš Janoušek
2012-02-13 9:25 ` Stanislaw Gruszka
2012-02-13 13:09 ` Stanislaw Gruszka
2012-02-13 13:29 ` Tomáš Janoušek
2012-02-14 9:20 ` Stanislaw Gruszka
2012-03-05 14:01 ` Tomáš Janoušek
2012-03-05 14:57 ` Stanislaw Gruszka
2012-03-05 15:00 ` Tomáš Janoušek
2012-03-05 15:11 ` Stanislaw Gruszka
2012-03-05 15:18 ` Tomáš Janoušek
2011-11-21 13:05 ` Stanislaw Gruszka
2011-11-21 13:09 ` Tomáš Janoušek
2011-11-21 13:40 ` Stanislaw Gruszka
2011-11-21 14:32 ` Tomáš Janoušek
2011-11-10 19:31 ` Adrian Chadd
2011-11-11 5:44 ` Stanislaw Gruszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EBC038C.1050700@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.com \
--cc=tomi@nomi.cz \
--cc=wey-yi.w.guy@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome