Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756069AbbEFBvy (ORCPT ); Tue, 5 May 2015 21:51:54 -0400 Received: from mx1.redhat.com ([209.132.183.28]:37672 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756044AbbEFBvr (ORCPT ); Tue, 5 May 2015 21:51:47 -0400 Date: Wed, 6 May 2015 09:51:35 +0800 From: Dave Young To: Joerg Roedel Cc: Baoquan He , "Li, ZhenHua" , dwmw2@infradead.org, indou.takao@jp.fujitsu.com, vgoyal@redhat.com, iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, kexec@lists.infradead.org, alex.williamson@redhat.com, ddutile@redhat.com, ishii.hironobu@jp.fujitsu.com, bhelgaas@google.com, doug.hatch@hp.com, jerry.hoemann@hp.com, tom.vaden@hp.com, li.zhang6@hp.com, lisa.mitchell@hp.com, billsumnerlinux@gmail.com, rwright@hp.com Subject: Re: [PATCH v10 0/10] iommu/vt-d: Fix intel vt-d faults in kdump kernel Message-ID: <20150506015135.GB14065@dhcp-128-4.nay.redhat.com> References: <20150415005731.GC19051@localhost.localdomain> <552DFB56.1070600@hp.com> <20150415064803.GF19051@localhost.localdomain> <20150424080147.GC4458@dhcp-16-116.nay.redhat.com> <20150424082528.GA23912@dhcp-128-91.nay.redhat.com> <20150424083530.GD4458@dhcp-16-116.nay.redhat.com> <20150424084957.GC23912@dhcp-128-91.nay.redhat.com> <20150504162318.GH15736@8bytes.org> <20150505061423.GC31063@dhcp-128-4.nay.redhat.com> <20150505153157.GQ15736@8bytes.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150505153157.GQ15736@8bytes.org> User-Agent: Mutt/1.5.22.1-rc1 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 861 Lines: 19 On 05/05/15 at 05:31pm, Joerg Roedel wrote: > On Tue, May 05, 2015 at 02:14:23PM +0800, Dave Young wrote: > > The failure is nothing different, but as I said in another reply the > > difference is we could use corrupted data to possiblly cause more failure. > > I still fail to see how things can get more worse than they already are > by reusing the old data (we just reuse it, we do not modify anything DMA write will modify system ram, if the old data is corrupted it is possible that DMA operation modify wrong ram regions because of wrong mapping. Am I missing something and is it not possible? Thanks Dave -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/