From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 2AETImLLEWBZTwAAWB0awg (envelope-from ) for ; Wed, 27 Jan 2021 15:21:54 -0500 Received: by simark.ca (Postfix, from userid 112) id 7621A1EF7A; Wed, 27 Jan 2021 15:21:54 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_NONE,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 Received: from sourceware.org (unknown [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 9EAFC1EF80 for ; Wed, 27 Jan 2021 15:21:53 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id C7A6E398B84A; Wed, 27 Jan 2021 20:21:50 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C7A6E398B84A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1611778910; bh=jcFMzYIF4imQAk4/JWUwfJRt3vaCNv2Xa6CGKUU+Ewc=; h=To:Subject:Date:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=AX0P3Su6UB1B95iA2xRqGTYRDKn3Inwn09Ezmnp82BZ2Tbki9TIbbCBpNLSyHdajJ Y0F5OL609livgskaoOcoO6SeJ6xczg4/b7yByjlq5v3xre7wtCgWsoSrCqdrTBElO/ wIKjxYKu1S2Xu7hVkq0dB04SnpZmnp9eqzDB7Nrc= Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) by sourceware.org (Postfix) with ESMTPS id 9B6BA398B84E for ; Wed, 27 Jan 2021 20:21:45 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 9B6BA398B84E Received: by mail-qk1-x730.google.com with SMTP id v126so3068476qkd.11 for ; Wed, 27 Jan 2021 12:21:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=jcFMzYIF4imQAk4/JWUwfJRt3vaCNv2Xa6CGKUU+Ewc=; b=NrmqTN8GEFep1BtDaQezy70HQE9nWRjwKpI6SjWb3oh+awshpyXyNpkns0aDG5WFin c63sOlcAO6Gx1o3PyaCJyMxCoRGT1Z/Lv05PIr7D+TO//kUabF7uGVKUo+6i2fxcu4IV 9Ro4afRVcHRgfwwZdwPvKv3loXrKdU8qQ6JaaHpI95uOoEQ576s42vnFHMzc9qmHi0L8 XYNPiD7leKvfIzsletXA5SBNIj2fVVqPBurgU8y2wqjHLfah5hhLZWSOK8zIyaPlFsmY fKKZpHGYEM1pcB26cYJqlj8/Fet7RKXwiwTu+LT2GWZ5OXe75Tbzj1ikXsfbTEL99dYx uiOg== X-Gm-Message-State: AOAM532w4RtrN6YgHDOB9ayrTtFQXoMdPVjg+R8DflMZSDKecuZxu7/h Pdo+E7GF/d7IuE6dzf5vna/h32jYgCk1cw== X-Google-Smtp-Source: ABdhPJy8SPjG1TvoQA89X48SdxLpAdQOVA3e6cfkzLesOrLB2cZiUMS1Td+jLmaWvB8mMteINMiClg== X-Received: by 2002:a37:d03:: with SMTP id 3mr12319088qkn.45.1611778905153; Wed, 27 Jan 2021 12:21:45 -0800 (PST) Received: from localhost.localdomain ([2804:7f0:8284:874d:b82c:87fc:4324:adab]) by smtp.gmail.com with ESMTPSA id b194sm1854531qkc.102.2021.01.27.12.21.44 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Jan 2021 12:21:44 -0800 (PST) To: gdb-patches@sourceware.org Subject: [PATCH v5 17/25] AArch64: Report tag violation error information Date: Wed, 27 Jan 2021 17:21:04 -0300 Message-Id: <20210127202112.2485702-18-luis.machado@linaro.org> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20210127202112.2485702-1-luis.machado@linaro.org> References: <20210127202112.2485702-1-luis.machado@linaro.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Luis Machado via Gdb-patches Reply-To: Luis Machado Errors-To: gdb-patches-bounces@sourceware.org Sender: "Gdb-patches" Updates on v4: - Print exception error. - Update function names. -- Whenever a memory tag violation occurs, we get a SIGSEGV. Additional information can be obtained through the siginfo data structure. For AArch64 the Linux kernel may expose the fault address and tag information, if we have a synchronous event. Otherwise there is no fault address available. The synchronous event looks like this: -- (gdb) continue Continuing. Program received signal SIGSEGV, Segmentation fault Memory tag violation while accessing address 0x0000fffff7ff8000 Allocation tag 0x1. -- The asynchronous event looks like this: -- (gdb) continue Continuing. Program received signal SIGSEGV, Segmentation fault Memory tag violation Fault address unavailable. -- gdb/ChangeLog: YYYY-MM-DD Luis Machado * aarch64-linux-tdep.c (aarch64_linux_report_signal_info): New function. (aarch64_linux_init_abi): Register aarch64_linux_report_signal_info as the report_signal_info hook. * arch/aarch64-linux.h (SEGV_MTEAERR): Define. (SEGV_MTESERR): Define. --- gdb/aarch64-linux-tdep.c | 66 ++++++++++++++++++++++++++++++++++++ gdb/arch/aarch64-mte-linux.h | 6 ++++ 2 files changed, 72 insertions(+) diff --git a/gdb/aarch64-linux-tdep.c b/gdb/aarch64-linux-tdep.c index 1063dd7a82..4ccee9c34e 100644 --- a/gdb/aarch64-linux-tdep.c +++ b/gdb/aarch64-linux-tdep.c @@ -1700,6 +1700,69 @@ aarch64_linux_memtag_to_string (struct gdbarch *gdbarch, return string_printf ("0x%s", phex_nz (tag, sizeof (tag))); } +/* AArch64 Linux implementation of the report_signal_info gdbarch + hook. Displays information about possible memory tag violations. */ + +static void +aarch64_linux_report_signal_info (struct gdbarch *gdbarch, + struct ui_out *uiout, + enum gdb_signal siggnal) +{ + struct gdbarch_tdep *tdep = gdbarch_tdep (gdbarch); + + if (!tdep->has_mte () || siggnal != GDB_SIGNAL_SEGV) + return; + + CORE_ADDR fault_addr = 0; + long si_code = 0; + + try + { + /* Sigcode tells us if the segfault is actually a memory tag + violation. */ + si_code = parse_and_eval_long ("$_siginfo.si_code"); + + fault_addr + = parse_and_eval_long ("$_siginfo._sifields._sigfault.si_addr"); + } + catch (const gdb_exception_error &exception) + { + exception_print (gdb_stderr, exception); + return; + } + + /* If this is not a memory tag violation, just return. */ + if (si_code != SEGV_MTEAERR && si_code != SEGV_MTESERR) + return; + + uiout->text ("\n"); + + uiout->field_string ("sigcode-meaning", _("Memory tag violation")); + + /* For synchronous faults, show additional information. */ + if (si_code == SEGV_MTESERR) + { + uiout->text (_(" while accessing address ")); + uiout->field_core_addr ("fault-addr", gdbarch, fault_addr); + uiout->text ("\n"); + + gdb::optional atag = aarch64_mte_get_atag (fault_addr); + + if (!atag.has_value ()) + uiout->text (_("Allocation tag unavailable")); + else + { + uiout->text (_("Allocation tag ")); + uiout->field_string ("allocation-tag", hex_string (*atag)); + } + } + else + { + uiout->text ("\n"); + uiout->text (_("Fault address unavailable")); + } +} + static void aarch64_linux_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch) { @@ -1780,6 +1843,9 @@ aarch64_linux_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch) /* Register a hook for converting a memory tag to a string. */ set_gdbarch_memtag_to_string (gdbarch, aarch64_linux_memtag_to_string); + + set_gdbarch_report_signal_info (gdbarch, + aarch64_linux_report_signal_info); } /* Initialize the aarch64_linux_record_tdep. */ diff --git a/gdb/arch/aarch64-mte-linux.h b/gdb/arch/aarch64-mte-linux.h index d44cae92a6..0f181a8595 100644 --- a/gdb/arch/aarch64-mte-linux.h +++ b/gdb/arch/aarch64-mte-linux.h @@ -35,6 +35,12 @@ #define AARCH64_MTE_LOGICAL_TAG_START_BIT 56 #define AARCH64_MTE_LOGICAL_MAX_VALUE 0xf +/* Memory tagging definitions. */ +#ifndef SEGV_MTEAERR +# define SEGV_MTEAERR 8 +# define SEGV_MTESERR 9 +#endif + /* Memory tag types for AArch64. */ enum class aarch64_memtag_type { -- 2.25.1