From: gengdongjiu <gengdongjiu@huawei.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Will Deacon <will.deacon@arm.com>
Cc: Tyler Baicar <tbaicar@codeaurora.org>, <lenb@kernel.org>,
<james.morse@arm.com>, <bp@suse.de>, <shiju.jose@huawei.com>,
<geliangtang@gmail.com>, <andriy.shevchenko@linux.intel.com>,
<tony.luck@intel.com>, <linux-acpi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <austinwc@codeaurora.org>
Subject: Re: [PATCH] acpi: apei: fix GHES estatus iteration
Date: Fri, 11 Aug 2017 06:04:16 +0800 [thread overview]
Message-ID: <5591b641-6eb0-0cb6-e74d-7e55cad5ee33@huawei.com> (raw)
In-Reply-To: <1971058.u9kdacGNiq@aspire.rjw.lan>
On 2017/8/9 8:52, Rafael J. Wysocki wrote:
> On Tuesday, August 8, 2017 6:32:20 PM CEST Will Deacon wrote:
>> On Thu, Aug 03, 2017 at 03:32:25PM -0600, Tyler Baicar wrote:
>>> Currently iterating through the GHES estatus blocks does not
>>> take into account the new generic data v3 structure size. This
>>> can result in garbage non-standard trace events to be triggered
>>> since the loop will not properly iterate through the estatus
>>> blocks and not properly terminate.
>>>
>>> Update the GHES estatus iteration to properly increment through
>>> the estatus blocks similar to how the CPER estatus printing
>>> iterates through them.
>>>
>>> Fixes: bbcc2e7b642e ("ras: acpi/apei: cper: add support for generic data v3 structure")
I do not think it has relationship with this "bbcc2e7b642e", the root cause is that it
does not consider the acpi_hest_generic_data_v300, this code exists long long time ago.
so please also review this patch:
https://lkml.org/lkml/2017/8/10/747
previously I do not see Tyler's this modification, just know see it.
>>> Signed-off-by: Tyler Baicar <tbaicar@codeaurora.org>
>>> Tested-by: Austin Christ <austinwc@codeaurora.org>
>>> ---
>>> drivers/acpi/apei/apei-internal.h | 5 -----
>>> drivers/acpi/apei/ghes.c | 8 +++++++-
>>> 2 files changed, 7 insertions(+), 6 deletions(-)
>>
>> Whilst much of the initial code here went through the arm64 tree in the
>> previous merge window, I'm assuming that Boris will take this fix via his
>> tree (likewise for "[PATCH V2] acpi: apei: clear error status before
>> acknowledging the error").
>
> Actually I will if Boris ACKs these.
>
> Thanks,
> Rafael
>
>
> .
>
next prev parent reply other threads:[~2017-08-10 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 21:32 Tyler Baicar
2017-08-08 16:32 ` Will Deacon
2017-08-09 0:52 ` Rafael J. Wysocki
2017-08-09 4:57 ` Borislav Petkov
2017-08-10 22:04 ` gengdongjiu [this message]
2017-08-11 13:17 ` Baicar, Tyler
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=5591b641-6eb0-0cb6-e74d-7e55cad5ee33@huawei.com \
--to=gengdongjiu@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=austinwc@codeaurora.org \
--cc=bp@suse.de \
--cc=geliangtang@gmail.com \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=shiju.jose@huawei.com \
--cc=tbaicar@codeaurora.org \
--cc=tony.luck@intel.com \
--cc=will.deacon@arm.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®