Netdev List
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Ruan Bahia <ruanmed@live.com>, <przemyslaw.kitszel@intel.com>
Cc: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
	<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
	<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [BUG] e1000e: incorrect modified flag check in e1000_read_nvm_spt() (Bugzilla #221729)
Date: Wed, 14 Oct 2026 14:08:24 -0700	[thread overview]
Message-ID: <9086c9d4-d2d4-4ea0-91ce-5eb047dd931d@intel.com> (raw)
In-Reply-To: <CPDP284MB39374BC5A0CD11C9253CABF7C79D2@CPDP284MB3937.BRAP284.PROD.OUTLOOK.COM>



On 10/14/2026 10:47 AM, Ruan Bahia wrote:
> Hi Tony and Przemek,
> 
> I am writing to bring Bugzilla #221729 to your attention (reported there 
> in 2026-07-06 19:39), as it describes a logic bug in 
> e1000_read_nvm_spt() that can cause silent shadow RAM corruption on SPT+ 
> PCH chips.
> 
> A fix for this was recently submitted to the intel-wired-lan list by Ivy 
> Lopez. I wanted to ensure the Bugzilla ticket is linked to this 
> discussion for tracking purposes.
> 
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=221729
> 
> Please let me know if any further information is needed from me.

Hi Ruan,

Thanks for the information. I've have it queued up; I'm waiting for room 
to send it. I'll let you know if anything else is needed.

Thanks,
Tony

> Thanks,
> 
> -- 
> Ruan Bahia


           reply	other threads:[~2026-10-14 21:08 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CPDP284MB39374BC5A0CD11C9253CABF7C79D2@CPDP284MB3937.BRAP284.PROD.OUTLOOK.COM>]

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=9086c9d4-d2d4-4ea0-91ce-5eb047dd931d@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=ruanmed@live.com \
    /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