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: <20110527071838.GA16217@kroah.com>
Date:	Fri, 27 May 2011 15:18:38 +0800
From:	Greg KH <greg@...ah.com>
To:	Mike Travis <travis@....com>
Cc:	David Woodhouse <dwmw2@...radead.org>,
	Chris Wright <chrisw@...s-sol.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>, linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	iommu@...ts.linux-foundation.org, Mike Habeck <habeck@....com>,
	stable@...nel.org
Subject: Re: [stable] [PATCH 1/7] Intel pci: Check for identity mapping
 candidate using system dma mask

On Thu, May 26, 2011 at 08:32:22PM -0500, Mike Travis wrote:
> 	The identity mapping code appears to make the assumption that
> 	if the devices dma_mask is greater than 32bits the device can
> 	use identity mapping.  But that is not true, take the case 
> 	where we have a 40bit device in a 44bit architecture.  The
> 	device can potentially receive a physical address that it
> 	will truncate and cause incorrect addresses to be used.
> 
> 	Instead check to see if the device's dma_mask is large enough
> 	to address the system's dma_mask.
> 
> From: Chris Wright <chrisw@...s-sol.org>
> Signed-off-by: Mike Travis <travis@....com>
> Reviewed-by: Mike Habeck <habeck@....com>
> ---
>  drivers/pci/intel-iommu.c |   15 +++++++++++++--
>  1 file changed, 13 insertions(+), 2 deletions(-)

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
for how to do this properly.

</formletter>

I'll not send this out for the other 6 patches that also do not follow
the proper format, as I'm sure you would get bored reading them.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ