From: "Baicar, Tyler" <tbaicar@codeaurora.org>
To: Dongjiu Geng <gengdongjiu@huawei.com>,
rjw@rjwysocki.net, lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] acpi: apei: fix the wrongly parse generic error status block
Date: Thu, 10 Aug 2017 11:48:00 -0600 [thread overview]
Message-ID: <9ea70eed-f743-0c8b-2a70-27ce4c0d8705@codeaurora.org> (raw)
In-Reply-To: <1502388412-20273-1-git-send-email-gengdongjiu@huawei.com>
Hello,
I have already posted a patch fixing this. Please see:
https://lkml.org/lkml/2017/8/3/824
This makes the loop identical to the CPER code which prints the estatus
blocks to the kernel logs.
Thanks,
Tyler
On 8/10/2017 12:06 PM, Dongjiu Geng wrote:
> The revision 0x300 generic error data entry is different with the old
> version. when ghes_do_proc traverses to get the data entry, it does not
> consider this difference. so when error status block has revision 0x300
> data entry, it will have issue.
>
> Signed-off-by: Dongjiu Geng <gengdongjiu@huawei.com>
> ---
> drivers/acpi/apei/apei-internal.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/acpi/apei/apei-internal.h b/drivers/acpi/apei/apei-internal.h
> index 6e9f14c0a71b..6491f1c4a96e 100644
> --- a/drivers/acpi/apei/apei-internal.h
> +++ b/drivers/acpi/apei/apei-internal.h
> @@ -122,8 +122,8 @@ struct dentry *apei_get_debugfs_dir(void);
>
> #define apei_estatus_for_each_section(estatus, section) \
> for (section = (struct acpi_hest_generic_data *)(estatus + 1); \
> - (void *)section - (void *)estatus < estatus->data_length; \
> - section = (void *)(section+1) + section->error_data_length)
> + (void *)section - (void *)(estatus + 1) < estatus->data_length; \
> + section = acpi_hest_get_next(section))
>
> static inline u32 cper_estatus_len(struct acpi_hest_generic_status *estatus)
> {
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-08-10 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 18:06 Dongjiu Geng
2017-08-10 17:48 ` Baicar, Tyler [this message]
2017-08-10 21:31 ` gengdongjiu
2017-08-10 21:37 ` gengdongjiu
2017-08-11 13:19 ` Baicar, Tyler
2017-08-11 23:41 ` gengdongjiu
2017-08-14 14:04 ` Baicar, Tyler
2017-08-15 1:14 ` gengdongjiu
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=9ea70eed-f743-0c8b-2a70-27ce4c0d8705@codeaurora.org \
--to=tbaicar@codeaurora.org \
--cc=gengdongjiu@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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®