Messages in this thread | | | Date | Tue, 20 Oct 2020 16:39:13 +0100 | From | Mark Brown <> | Subject | Re: [RFC PATCH 0/3] arm64: Implement reliable stack trace |
| |
On Mon, Oct 19, 2020 at 06:41:55PM -0500, Josh Poimboeuf wrote: > On Fri, Oct 16, 2020 at 01:15:34PM +0100, Mark Brown wrote:
> > Ah, I'd have interpreted "defined thread entry point" as meaning > > expecting to find specific functions appering at the end of the stack > > rather than meaning positively identifying the end of the stack - for > > arm64 we use a NULL frame pointer to indicate this in all situations. > > In that case that's one bit that is already clear.
> I think a NULL frame pointer isn't going to be robust enough. For > example NULL could easily be introduced by a corrupt stack, or by asm > frame pointer misuse.
Is it just the particular poison value that you're concerned about here or are you looking for additional checks of some other kind? [unhandled content-type:application/pgp-signature] | |