From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: <netdev@vger.kernel.org>, Kelvin Kang <kelvin.kang@intel.com>,
"Arkadiusz Kubalewski" <arkadiusz.kubalewski@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>
Subject: Re: [PATCH iwl-net v3] i40e: fix hot issue NVM content is corrupted after nvmupdate
Date: Thu, 13 Jun 2024 14:27:14 -0700 [thread overview]
Message-ID: <03515112-e2b5-4bdb-aebb-16797a59b3fa@intel.com> (raw)
In-Reply-To: <20240612110402.3356700-1-aleksandr.loktionov@intel.com>
On 6/12/2024 4:04 AM, Aleksandr Loktionov wrote:
As Przemek has pointed out...
"hot issue" doesn't necessarily carry the same meaning; better to just
drop that out of the title.
> The bug affects users only at the time when they try to update NVM, and
> only F/W versions that generate errors while nvmupdate. For example X710DA2
> with 0x8000ECB7 F/W is affected, but there are probably more...
>
> After 230f3d53a547 patch, which should only replace F/W specific error codes
Could you cite the commit in the preferred style of SHA +title?
I'd suggest
'After commit 230f3d53a547 ("i40e: remove i40e_status"),'
Thanks,
Tony
> with Linux kernel generic, all EIO errors started to be converted into EAGAIN
> which leads nvmupdate to retry until it timeouts and sometimes fails after
> more than 20 minutes in the middle of NVM update, so NVM becomes corrupted.
>
> Remove wrong EIO to EGAIN conversion and pass all errors as is.
>
> Fixes: 230f3d53a547 ("i40e: remove i40e_status")
> Co-developed-by: Kelvin Kang <kelvin.kang@intel.com>
> Signed-off-by: Kelvin Kang <kelvin.kang@intel.com>
> Reviewed-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
> Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
next prev parent reply other threads:[~2024-06-13 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 11:04 [PATCH iwl-net v3] i40e: fix hot issue NVM content is corrupted after nvmupdate Aleksandr Loktionov
2024-06-13 14:45 ` [Intel-wired-lan] " Brelinski, Tony
2024-06-13 21:27 ` Tony Nguyen [this message]
2024-06-14 6:57 ` Loktionov, Aleksandr
2024-06-14 7:43 ` [Intel-wired-lan] " Paul Menzel
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=03515112-e2b5-4bdb-aebb-16797a59b3fa@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kelvin.kang@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.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;
as well as URLs for NNTP newsgroup(s).