linux-kernel - Re: inode->i_wb

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: <20120312211333.GB20204@zod.bos.redhat.com>
Date:	Mon, 12 Mar 2012 17:13:33 -0400
From:	Josh Boyer <jwboyer@...hat.com>
To:	Keith Packard <keithp@...thp.com>
Cc:	Dave Jones <davej@...hat.com>, Yang Bai <hamo.by@...il.com>,
	Fengguang Wu <fengguang.wu@...el.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Fedora Kernel Team <kernel-team@...oraproject.org>,
	kernel@...arici.cz, David Woodhouse <dwmw2@...radead.org>
Subject: Re: inode->i_wb_list corruption.

On Fri, Mar 09, 2012 at 02:44:49PM -0800, Keith Packard wrote:
> <#part sign=pgpmime>
> On Fri, 9 Mar 2012 15:19:34 -0500, Josh Boyer <jwboyer@...hat.com> wrote:
> 
> > Is the VT-d issue something in the hardware itself, or do you mean if
> > you have it enabled in the kernel?  We've had the intel IOMMU disabled
> > by default in the Fedora kernels for a while now.  At least since before
> > 3.2 was released.
> 
> I don't know for sure; David Woodhouse gave a scary presentation
> yesterday that makes me unsure of what happens when IOMMU is disabled in
> the kernel, given that much of the hardware is setup by the BIOS.

Is that presentation something that could be shared?  I have to say,
hearing that doesn't really inspire confidence in either the IOMMU or
the kernel.

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