qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Ani Sinha <anisinha@redhat.com>,
	Dongjiu Geng <gengdongjiu1@gmail.com>,
	linux-kernel@vger.kernel.org, qemu-arm@nongnu.org,
	qemu-devel@nongnu.org
Subject: Re: [PATCH v2 12/15] acpi/ghes: don't crash QEMU if ghes GED is not found
Date: Wed, 2 Oct 2024 14:46:30 +0200	[thread overview]
Message-ID: <20241002144630.1f8b68c1@imammedo.users.ipa.redhat.com> (raw)
In-Reply-To: <18c69e8c7a6b6ac365397fe1f442f3ba0cb83be8.1727766088.git.mchehab+huawei@kernel.org>

On Tue,  1 Oct 2024 09:03:49 +0200
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:

> Instead, produce an error and continue working

s/^^^^/make error handling within ... consistent, i.e. instead abort just print a error in case ... /


> 
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
>  hw/acpi/ghes.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/hw/acpi/ghes.c b/hw/acpi/ghes.c
> index 3af1cd16d4d7..209095f67e9a 100644
> --- a/hw/acpi/ghes.c
> +++ b/hw/acpi/ghes.c
> @@ -418,7 +418,10 @@ void ghes_record_cper_errors(const void *cper, size_t len,
>  
>      acpi_ged_state = ACPI_GED(object_resolve_path_type("", TYPE_ACPI_GED,
>                                                         NULL));
> -    g_assert(acpi_ged_state);
> +    if (!acpi_ged_state) {
> +        error_setg(errp, "Can't find ACPI_GED object");
> +        return;
> +    }
>      ags = &acpi_ged_state->ghes_state;
>  
>      get_ghes_offsets(le64_to_cpu(ags->ghes_addr_le),



  reply	other threads:[~2024-10-02 12:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01  7:03 [PATCH v2 00/15] Prepare GHES driver to support error injection Mauro Carvalho Chehab
2024-10-01  7:03 ` [PATCH v2 01/15] acpi/ghes: get rid of ACPI_HEST_SRC_ID_RESERVED Mauro Carvalho Chehab
2024-10-01  7:03 ` [PATCH v2 02/15] acpi/ghes: simplify acpi_ghes_record_errors() code Mauro Carvalho Chehab
2024-10-01  7:03 ` [PATCH v2 03/15] acpi/ghes: simplify the per-arch caller to build HEST table Mauro Carvalho Chehab
2024-10-02 13:30   ` Igor Mammedov
2024-10-01  7:03 ` [PATCH v2 04/15] acpi/ghes: better handle source_id and notification Mauro Carvalho Chehab
2024-10-02 13:28   ` Igor Mammedov
2024-10-01  7:03 ` [PATCH v2 05/15] acpi/ghes: Fix acpi_ghes_record_errors() argument Mauro Carvalho Chehab
2024-10-02 13:21   ` Igor Mammedov
2024-10-01  7:03 ` [PATCH v2 06/15] acpi/ghes: Remove a duplicated out of bounds check Mauro Carvalho Chehab
2024-10-01  7:03 ` [PATCH v2 07/15] acpi/ghes: Change the type for source_id Mauro Carvalho Chehab
2024-10-02 12:27   ` Igor Mammedov
2024-10-01  7:03 ` [PATCH v2 08/15] acpi/ghes: Prepare to support multiple sources on ghes Mauro Carvalho Chehab
2024-10-02 12:57   ` Igor Mammedov
2024-10-01  7:03 ` [PATCH v2 09/15] acpi/ghes: make the GHES record generation more generic Mauro Carvalho Chehab
2024-10-02 13:14   ` Igor Mammedov
2024-10-01  7:03 ` [PATCH v2 10/15] acpi/ghes: move offset calculus to a separate function Mauro Carvalho Chehab
2024-10-02 13:20   ` Igor Mammedov
2024-10-01  7:03 ` [PATCH v2 11/15] acpi/ghes: better name GHES memory error function Mauro Carvalho Chehab
2024-10-01  7:03 ` [PATCH v2 12/15] acpi/ghes: don't crash QEMU if ghes GED is not found Mauro Carvalho Chehab
2024-10-02 12:46   ` Igor Mammedov [this message]
2024-10-01  7:03 ` [PATCH v2 13/15] acpi/ghes: rename etc/hardware_error file macros Mauro Carvalho Chehab
2024-10-01  7:03 ` [PATCH v2 14/15] acpi/ghes: better name the offset of the hardware error firmware Mauro Carvalho Chehab
2024-10-02 12:38   ` Igor Mammedov
2024-10-01  7:03 ` [PATCH v2 15/15] docs: acpi_hest_ghes: fix documentation for CPER size Mauro Carvalho Chehab

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=20241002144630.1f8b68c1@imammedo.users.ipa.redhat.com \
    --to=imammedo@redhat.com \
    --cc=anisinha@redhat.com \
    --cc=gengdongjiu1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mst@redhat.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).