From: Bjorn Helgaas <helgaas@kernel.org>
To: Alexey Bogoslavsky <Alexey.Bogoslavsky@wdc.com>
Cc: Keith Busch <kbusch@kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Bjorn Helgas <bhelgaas@google.com>,
Christoph Hellwig <hch@lst.de>,
Grant Grundler <grundler@chromium.org>,
Rajat Khandelwal <rajat.khandelwal@linux.intel.com>
Subject: Re: [PATCH 1/1] PCI/AER: Ignore correctable error reports for SN730 WD SSD
Date: Fri, 28 Apr 2023 17:00:54 -0500 [thread overview]
Message-ID: <20230428220054.GA369990@bhelgaas> (raw)
In-Reply-To: <DM6PR04MB64739F4EE26DB3E95BA8D1788B679@DM6PR04MB6473.namprd04.prod.outlook.com>
On Mon, Apr 24, 2023 at 11:27:43AM +0000, Alexey Bogoslavsky wrote:
> Hello Bjorn,
>
> Sorry for not addressing your questions earlier. As you may have
> heard, WD experienced a hacking attack which left us with no access
> to the company e-mail for weeks.
So sorry to hear that, that is incredibly disruptive.
> As for the patch, no FW change was an option as the product causing
> the issue was basically at the end of life. So, I prepared a
> workaround that took into account all the comments from the
> community.
Makes sense and is a very common situation. In general we try to
avoid "fixing" issues by requiring a firmware update because even if
such an update is available, most users will not have it.
I think the hope was that a kernel quirk could tweak something on the
device to make it stop reporting these errors.
> Yet, at this point it seems like the company has lost interest in
> promoting this patch altogether. So we could just drop it. Please
> let me know if there's anything I need to do to request that
> officially.
No worries, you don't need to do anything. If you can point me to any
users or bug reports, maybe I can tidy this up and merge it. Those
users are still being annoyed by the error spam, and that seems
pointless.
Bjorn
prev parent reply other threads:[~2023-04-28 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BY5PR04MB704131DBB47254C9F1FF12B38B409@BY5PR04MB7041.namprd04.prod.outlook.com>
2023-01-16 18:32 ` [PATCH 1/1] PCI/AER: Ignore correctable error reports for SN730 WD SSD Alexey Bogoslavsky
2023-01-17 7:14 ` 'hch@lst.de'
2023-01-17 13:20 ` Alexey Bogoslavsky
2023-01-17 14:22 ` Bjorn Helgaas
2023-01-17 18:06 ` Alexey Bogoslavsky
2023-01-17 15:54 ` Keith Busch
2023-01-17 18:15 ` Alexey Bogoslavsky
2023-04-11 22:15 ` Bjorn Helgaas
2023-04-24 11:27 ` Alexey Bogoslavsky
2023-04-28 22:00 ` Bjorn Helgaas [this message]
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=20230428220054.GA369990@bhelgaas \
--to=helgaas@kernel.org \
--cc=Alexey.Bogoslavsky@wdc.com \
--cc=bhelgaas@google.com \
--cc=grundler@chromium.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rajat.khandelwal@linux.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