From: Greg KH <gregkh@suse.de>
To: linux-kernel@vger.kernel.org, stable@kernel.org
Cc: stable-review@kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk,
Tejun Heo <tj@kernel.org>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Matteo Frigo <athena@fftw.org>, Ingo Molnar <mingo@elte.hu>
Subject: [12/18] x86: Fix iommu=nodac parameter handling
Date: Wed, 16 Dec 2009 16:46:03 -0800 [thread overview]
Message-ID: <20091217004708.677324097@mini.kroah.org> (raw)
In-Reply-To: <20091217005306.GA6230@kroah.com>
2.6.27-stable review patch. If anyone has any objections, please let us know.
------------------
From: Tejun Heo <tj@kernel.org>
commit 2ae8bb75db1f3de422eb5898f2a063c46c36dba8 upstream.
iommu=nodac should forbid dac instead of enabling it. Fix it.
Signed-off-by: Tejun Heo <tj@kernel.org>
Acked-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: Matteo Frigo <athena@fftw.org>
LKML-Reference: <4AE5B52A.4050408@kernel.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
---
arch/x86/kernel/pci-dma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/arch/x86/kernel/pci-dma.c
+++ b/arch/x86/kernel/pci-dma.c
@@ -175,7 +175,7 @@ static __init int iommu_setup(char *p)
if (!strncmp(p, "allowdac", 8))
forbid_dac = 0;
if (!strncmp(p, "nodac", 5))
- forbid_dac = -1;
+ forbid_dac = 1;
if (!strncmp(p, "usedac", 6)) {
forbid_dac = -1;
return 1;
next prev parent reply other threads:[~2009-12-17 0:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 0:53 [00/18] 2.6.27.42-stable review Greg KH
2009-12-17 0:45 ` [01/18] signal: Fix alternate signal stack check Greg KH
2009-12-17 0:45 ` [02/18] debugfs: fix create mutex racy fops and private data Greg KH
2009-12-17 0:45 ` [03/18] firewire: ohci: handle receive packets with a data length of zero Greg KH
2009-12-17 0:45 ` [04/18] fuse: reject O_DIRECT flag also in fuse_create Greg KH
2009-12-17 1:36 ` David Daney
2009-12-17 4:15 ` Greg KH
2009-12-17 0:45 ` [05/18] hfs: fix a potential buffer overflow Greg KH
2009-12-17 0:45 ` [06/18] pata_hpt{37x|3x2n}: fix timing register masks (take 2) Greg KH
2009-12-17 0:45 ` [07/18] ssb: Fix range check in sprom write Greg KH
2009-12-17 0:45 ` [08/18] V4L/DVB: Fix test in copy_reg_bits() Greg KH
2009-12-17 0:46 ` [09/18] x86, apic: Enable lapic nmi watchdog on AMD Family 11h Greg KH
2009-12-17 0:46 ` [10/18] x86: ASUS P4S800 reboot=bios quirk Greg KH
2009-12-17 0:46 ` [11/18] x86, Calgary IOMMU quirk: Find nearest matching Calgary while walking up the PCI tree Greg KH
2009-12-17 0:46 ` Greg KH [this message]
2009-12-17 0:46 ` [13/18] x86: GART: pci-gart_64.c: Use correct length in strncmp Greg KH
2009-12-17 0:46 ` [14/18] [IA64] fix csum_ipv6_magic() Greg KH
2009-12-17 0:46 ` [15/18] USB: fix mos7840 problem with minor numbers Greg KH
2009-12-17 0:46 ` [16/18] backlight: lcd - Fix wrong sizeof Greg KH
2009-12-17 0:46 ` [17/18] jffs2: Fix long-standing bug with symlink garbage collection Greg KH
2009-12-17 0:46 ` [18/18] matroxfb: fix problems with display stability Greg KH
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=20091217004708.677324097@mini.kroah.org \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=athena@fftw.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable-review@kernel.org \
--cc=stable@kernel.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®