From: "Madhavan T. Venkataraman" <madvenka@linux•microsoft.com>
To: Mark Brown <broonie@kernel•org>, Mark Rutland <mark.rutland@arm•com>
Cc: jpoimboe@redhat•com, ardb@kernel•org, nobuta.keiya@fujitsu•com,
catalin.marinas@arm•com, will@kernel•org, jmorris@namei•org,
pasha.tatashin@soleen•com, jthierry@redhat•com,
linux-arm-kernel@lists•infradead.org,
live-patching@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [RFC PATCH v5 0/2] arm64: Implement stack trace reliability checks
Date: Fri, 4 Jun 2021 15:44:39 -0500 [thread overview]
Message-ID: <3e3fdff0-26ed-e786-e570-3f569bda1609@linux.microsoft.com> (raw)
In-Reply-To: <20210604152908.GD4045@sirena.org.uk>
Hi Mark Rutland,
Could you please review this patch series when you get a chance?
I would really like to get a confirmation from you that there
are no gaps in this.
Thanks in advance!
Madhavan
On 6/4/21 10:29 AM, Mark Brown wrote:
> On Wed, May 26, 2021 at 04:49:15PM -0500, madvenka@linux•microsoft.com wrote:
>> From: "Madhavan T. Venkataraman" <madvenka@linux•microsoft.com>
>>
>> There are a number of places in kernel code where the stack trace is not
>> reliable. Enhance the unwinder to check for those cases and mark the
>> stack trace as unreliable. Once all of the checks are in place, the unwinder
>
> Reviewed-by: Mark Brown <broonie@kernel•org>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-06-04 20:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ea0ef9ed6eb34618bcf468fbbf8bdba99e15df7d>
2021-05-26 21:49 ` [RFC PATCH v5 0/2] arm64: Implement stack trace reliability checks madvenka
2021-05-26 21:49 ` [RFC PATCH v5 1/2] arm64: Introduce stack trace reliability checks in the unwinder madvenka
2021-06-24 14:40 ` Mark Rutland
2021-06-24 16:03 ` Mark Brown
2021-06-25 15:39 ` Madhavan T. Venkataraman
2021-06-25 15:51 ` Mark Brown
2021-06-25 17:05 ` Madhavan T. Venkataraman
2021-06-25 17:18 ` Madhavan T. Venkataraman
2021-06-26 15:35 ` Madhavan T. Venkataraman
2021-06-29 16:47 ` Josh Poimboeuf
2021-05-26 21:49 ` [RFC PATCH v5 2/2] arm64: Create a list of SYM_CODE functions, check return PC against list madvenka
2021-06-04 16:24 ` Mark Brown
2021-06-04 20:38 ` Madhavan T. Venkataraman
2021-06-04 16:59 ` Mark Brown
2021-06-04 20:40 ` Madhavan T. Venkataraman
2021-06-16 1:52 ` Suraj Jitindar Singh
2021-06-16 9:15 ` nobuta.keiya
2021-06-16 11:10 ` Madhavan T. Venkataraman
2021-06-04 15:29 ` [RFC PATCH v5 0/2] arm64: Implement stack trace reliability checks Mark Brown
2021-06-04 20:44 ` Madhavan T. Venkataraman [this message]
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=3e3fdff0-26ed-e786-e570-3f569bda1609@linux.microsoft.com \
--to=madvenka@linux$(echo .)microsoft.com \
--cc=ardb@kernel$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=catalin.marinas@arm$(echo .)com \
--cc=jmorris@namei$(echo .)org \
--cc=jpoimboe@redhat$(echo .)com \
--cc=jthierry@redhat$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=live-patching@vger$(echo .)kernel.org \
--cc=mark.rutland@arm$(echo .)com \
--cc=nobuta.keiya@fujitsu$(echo .)com \
--cc=pasha.tatashin@soleen$(echo .)com \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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