public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Tyler Baicar <tbaicar@codeaurora.org>
To: Qiang Zheng <zhengqiang10@huawei.com>,
	will.deacon@arm.com, james.morse@arm.com, shiju.jose@huawei.com,
	rjw@rjwysocki.net
Cc: gengdongjiu@huawei.com, wangxiongfeng2@huawei.com,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linuxarm@huawei.com
Subject: Re: [PATCH] Bug fix: Clear ack of GHES table which contain wrong Error status block, let new error can fill GHES table.
Date: Mon, 30 Oct 2017 09:53:39 -0400	[thread overview]
Message-ID: <61027894-b8ab-b90d-05fa-c8a04acfa42d@codeaurora.org> (raw)
In-Reply-To: <1509326594-201050-1-git-send-email-zhengqiang10@huawei.com>

On 10/29/2017 9:23 PM, Qiang Zheng wrote:
> Current Error status block processing flow, if wrong format is checked,
> GHES table ack is not cleared.
> It will cause new error can not be filled GHES table, because UEFI
> need check ack to know if error was handled by OS.
>
> This patch solved issue, no matter Error status block format is wrong,
> But GHES table format is corrected, we clear ack.
>
> Signed-off-by: Qiang Zheng <zhengqiang10@huawei.com>
> ---
>   drivers/acpi/apei/ghes.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c
> index 077f9ba..b0e0782 100644
> --- a/drivers/acpi/apei/ghes.c
> +++ b/drivers/acpi/apei/ghes.c
> @@ -743,6 +743,7 @@ static int ghes_proc(struct ghes *ghes)
>   	}
>   	ghes_do_proc(ghes, ghes->estatus);
>   
> +out:
The out goto is already at this location. Please sync to the tip:

         ghes_do_proc(ghes, ghes->estatus);

out:
         ghes_clear_estatus(ghes);

         if (rc == -ENOENT)
                 return rc;

         /*
          * GHESv2 type HEST entries introduce support for error acknowledgment,
          * so only acknowledge the error if this support is present.
          */
         if (is_hest_type_generic_v2(ghes))
                 return ghes_ack_error(ghes->generic_v2);

         return rc;


>   	/*
>   	 * GHESv2 type HEST entries introduce support for error acknowledgment,
>   	 * so only acknowledge the error if this support is present.
> @@ -752,7 +753,7 @@ static int ghes_proc(struct ghes *ghes)
>   		if (rc)
>   			return rc;
>   	}
> -out:
> +
>   	ghes_clear_estatus(ghes);
>   	return rc;
>   }

-- 
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.


  reply	other threads:[~2017-10-30 13:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30  1:23 [PATCH] Bug fix: Clear ack of GHES table which contain wrong Error status block, let new error can fill GHES table Qiang Zheng
2017-10-30 13:53 ` Tyler Baicar [this message]
2017-10-31  8:22   ` Zhengqiang

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=61027894-b8ab-b90d-05fa-c8a04acfa42d@codeaurora.org \
    --to=tbaicar@codeaurora.org \
    --cc=gengdongjiu@huawei.com \
    --cc=james.morse@arm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=rjw@rjwysocki.net \
    --cc=shiju.jose@huawei.com \
    --cc=wangxiongfeng2@huawei.com \
    --cc=will.deacon@arm.com \
    --cc=zhengqiang10@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