[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210115164718.GE44111@C02TD0UTHF1T.local>
Date: Fri, 15 Jan 2021 16:47:18 +0000
From: Mark Rutland <mark.rutland@....com>
To: Mark Brown <broonie@...nel.org>
Cc: Josh Poimboeuf <jpoimboe@...hat.com>, linux-kernel@...r.kernel.org,
Jiri Kosina <jikos@...nel.org>,
Joe Lawrence <joe.lawrence@...hat.com>,
Jonathan Corbet <corbet@....net>,
Miroslav Benes <mbenes@...e.cz>,
Petr Mladek <pmladek@...e.com>, linux-doc@...r.kernel.org,
live-patching@...r.kernel.org, linux-doc@...rt.kernel.org
Subject: Re: [PATCH v3] Documentation: livepatch: document reliable stacktrace
Hi Mark,
On Fri, Jan 15, 2021 at 02:24:46PM +0000, Mark Brown wrote:
> +.. Table of Contents:
> +
> + 1. Introduction
> + 2. Requirements
> + 3. Considerations
> + 3.1 Identifying successful termination
> + 3.2 Identifying unwindable code
> + 3.3 Unwinding across interrupts and exceptions
> + 3.4 Rewriting of return addresses
> + 3.5 Obscuring of return addresses
> + 3.6 Link register unreliability
>
It looks like we forgot to update this with the addition of the new
section 3, so this needs a trivial update to add that and fix the
numbering.
Otherwise this looks good; thanks for taking this off my hands! :)
Mark.
Powered by blists - more mailing lists