mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: liulongfang <liulongfang@huawei.com>,
	Oliver Neukum <oneukum@suse.com>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB:bugfix a controller halt error
Date: Thu, 27 Jul 2023 10:46:05 +0200	[thread overview]
Message-ID: <2fbd21f3-2da0-5a10-23c4-fcfecfe48311@suse.com> (raw)
In-Reply-To: <f03958f4-de73-ec43-fa13-02727b6018c3@huawei.com>

On 27.07.23 09:00, liulongfang wrote:
> On 2023/7/26 19:16, Oliver Neukum wrote:

>> 1. temporary - that is you have detected memory corruption but the RAM cell is not broken
>> 2. unrecoverable - that is we have lost data
>> 3. locateable - that is you know it hit the buffer of this operation and only it
>>
>> Am I correct so far?
>>
> You are right about the testing process.
> But this problem can exist in the real environment, just the probability of
> occurrence is very low.

Understood. Bit flips are random.

But this leaves two open questions.

1. How is the error reported

2. How are we supposed to handle it

Firstly, if we already know that there is an ECC failure
on the host we can use a specific error code and can check
for that.

Secondly, does this mean that the affected memory location
must not be touched until the machine is power cycled
or does it simply mean that the buffer is invalid?

> Our test tool only simulates that external interference destroys this part
> of the data in the buffer on the ECC memory. Even without this testing tool.
> This problem may also occur on real business hardware devices.

Understood. But what is the correct remedy if teh problem strikes
for real?

	Regards
		Oliver

  reply	other threads:[~2023-07-27  9:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 10:00 liulongfang
2023-07-21 11:08 ` Greg KH
2023-07-26  6:44   ` liulongfang
2023-07-26  7:18     ` Greg KH
2023-07-26 11:16       ` Oliver Neukum
2023-07-27  7:00         ` liulongfang
2023-07-27  8:46           ` Oliver Neukum [this message]
2023-07-27  4:02       ` liulongfang
2023-07-21 14:57 ` Alan Stern
2023-07-24 12:35   ` Oliver Neukum
2023-07-26  6:58   ` liulongfang
2023-07-26 14:20     ` Alan Stern
2023-07-27  7:03       ` liulongfang
2023-07-27  8:47         ` Oliver Neukum
2023-07-27 14:42         ` Alan Stern
2023-07-27 15:31           ` Oliver Neukum
2023-07-27 15:57             ` Alan Stern
2023-08-10  1:20               ` liulongfang

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=2fbd21f3-2da0-5a10-23c4-fcfecfe48311@suse.com \
    --to=oneukum@suse.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=liulongfang@huawei.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

all inboxes | Powered by JetHome®