From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751825AbYLSQRb (ORCPT ); Fri, 19 Dec 2008 11:17:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751479AbYLSQRH (ORCPT ); Fri, 19 Dec 2008 11:17:07 -0500 Received: from mail.suse.de ([195.135.220.2]:36742 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751466AbYLSQRG (ORCPT ); Fri, 19 Dec 2008 11:17:06 -0500 Date: Fri, 19 Dec 2008 08:14:40 -0800 From: Greg KH To: Pavel Machek Cc: linux-kernel@vger.kernel.org, stable@kernel.org, Justin Forbes , Zwane Mwaikambo , "Theodore Ts'o" , Randy Dunlap , Dave Jones , Chuck Wolber , Chris Wedgwood , Michael Krufky , Chuck Ebbert , Domenico Andreoli , Willy Tarreau , Rodrigo Rubira Branco , Jake Edge , Eugene Teo , torvalds@linux-foundation.org, akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk, Joerg Roedel Subject: Re: [patch 01/22] AMD IOMMU: enable device isolation per default Message-ID: <20081219161440.GB12492@suse.de> References: <20081216235704.347182084@mini.kroah.org> <20081217000353.GB4504@kroah.com> <20081218130015.GA1420@ucw.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081218130015.GA1420@ucw.cz> User-Agent: Mutt/1.5.16 (2007-06-09) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 18, 2008 at 02:00:15PM +0100, Pavel Machek wrote: > On Tue 2008-12-16 16:03:53, Greg KH wrote: > > 2.6.27-stable review patch. If anyone has any objections, please let us know. > > > > ------------------ > > > > From: Joerg Roedel > > > > commit 3ce1f93c6d53c3f91c3846cf66b018276c8ac2e7 upstream. > > > > Impact: makes device isolation the default for AMD IOMMU > > > > Some device drivers showed double-free bugs of DMA memory while testing > > them with AMD IOMMU. If all devices share the same protection domain > > this can lead to data corruption and data loss. Prevent this by putting > > each device into its own protection domain per default. > > > > Signed-off-by: Joerg Roedel > > Signed-off-by: Greg Kroah-Hartman > > This does not look like 'fix for a serious bug' to > me. stable_kernel_rules.txt says '...not a "this could be a problem" > type thing'. This is a serious bug, loosing data and crashing drivers seems serious to me. There was at least one bug report about this problem, and the change is upstream and simple and obvious. thanks, greg k-h