From: Arjan van de Ven <arjan@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
jeff@garzik.org, davem@davemloft.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Bruce Allan <bruce.w.allan@intel.com>
Subject: Re: [PATCH] e1000e: write protect ICHx NVM to prevent malicious write/erase
Date: Wed, 01 Oct 2008 18:33:31 -0700 [thread overview]
Message-ID: <48E424EB.1000204@linux.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0810011731350.3341@nehalem.linux-foundation.org>
Linus Torvalds wrote:
>
> On Wed, 1 Oct 2008, Jesse Brandeburg wrote:
>> From: Bruce Allan <bruce.w.allan@intel.com>
>>
>> Set the hardware to ignore all write/erase cycles to the GbE region in
>> the ICHx NVM. This feature can be disabled by the WriteProtectNVM module
>> parameter (enabled by default) only after a hardware reset, but
>> the machine must be power cycled before trying to enable writes.
>
> Thanks, applied.
>
> One thing that I did notice when I looked at the driver is that I don't
> see any serialization what-so-ever around a lot of the special accesses.
>
there's quite a few of that yes.
These are all fixed afaik but these fixes are being queued for 2.6.28 rather than being snuck in late into .27
(the patches have been posted to lkml a few times the last week)
next prev parent reply other threads:[~2008-10-02 1:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 0:18 [PATCH 2.6.27-rc8 0/1] e1000e nvm fix Jesse Brandeburg
2008-10-02 0:18 ` [PATCH] e1000e: write protect ICHx NVM to prevent malicious write/erase Jesse Brandeburg
2008-10-02 0:42 ` Linus Torvalds
2008-10-02 1:33 ` Arjan van de Ven [this message]
2008-10-02 9:05 ` Thomas Gleixner
2008-10-02 9:59 ` Jiri Kosina
2008-10-02 13:02 ` Jiri Kosina
2008-10-02 15:37 ` Brandeburg, Jesse
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=48E424EB.1000204@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).