Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754067AbYJATOT (ORCPT ); Wed, 1 Oct 2008 15:14:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752964AbYJATOJ (ORCPT ); Wed, 1 Oct 2008 15:14:09 -0400 Received: from mga01.intel.com ([192.55.52.88]:51534 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753111AbYJATOI convert rfc822-to-8bit (ORCPT ); Wed, 1 Oct 2008 15:14:08 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.33,344,1220252400"; d="scan'208";a="622340288" From: "Allan, Bruce W" To: Jiri Kosina CC: "Brandeburg, Jesse" , "linux-kernel@vger.kernel.org" , "linux-netdev@vger.kernel.org" , "kkeil@suse.de" , "agospoda@redhat.com" , "arjan@linux.intel.com" , "Graham, David" , "Ronciak, John" , Thomas Gleixner , "chris.jones@canonical.com" , "tim.gardner@intel.com" , "airlied@gmail.com" , Olaf Kirch Date: Wed, 1 Oct 2008 12:13:53 -0700 Subject: RE: [RFC PATCH 11/12] e1000e: write protect ICHx NVM to prevent malicious write/erase Thread-Topic: [RFC PATCH 11/12] e1000e: write protect ICHx NVM to prevent malicious write/erase Thread-Index: AckjydM2AHRM+RkKR0yrSLV3FhLFIwAFkl9A Message-ID: References: <20080930030825.22950.18891.stgit@jbrandeb-bw.jf.intel.com> <20080930032013.22950.70966.stgit@jbrandeb-bw.jf.intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 818 Lines: 21 On Wednesday, October 01, 2008 6:29 AM, Jiri Kosina wrote: > >Olaf raised a rather interesting question -- would iAMT be >able to access >NVM contents directly, even if the lock bit would be set on the device? >I.e. is iAMT allowed direct access to the EEPROM contents, bypassing >shadow ram mappings? > >Thanks, > >-- >Jiri Kosina >SUSE Labs > Only write/erase accesses are blocked by hardware after the protected range and lockdown bits are set in this patch; reads are still allowed. I just received confirmation that iAMT does not write to the GbE region of the NVM. -- 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/