From: Miroslav Benes <mbenes@suse.cz>
To: Vasily Gorbik <gor@linux.ibm.com>
Cc: heiko.carstens@de.ibm.com, borntraeger@de.ibm.com,
jpoimboe@redhat.com, joe.lawrence@redhat.com,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
jikos@kernel.org, pmladek@suse.com, nstange@suse.de,
live-patching@vger.kernel.org
Subject: Re: [PATCH v4 1/2] s390/unwind: add stack pointer alignment sanity checks
Date: Fri, 29 Nov 2019 19:16:45 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.21.1911291533310.23789@pobox.suse.cz> (raw)
In-Reply-To: <patch-1.thread-a0061f.git-617139935cc4.your-ad-here.call-01575012971-ext-9115@work.hours>
On Fri, 29 Nov 2019, Vasily Gorbik wrote:
> From: Miroslav Benes <mbenes@suse.cz>
>
> ABI requires SP to be aligned 8 bytes, report unwinding error otherwise.
>
> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
Signed-off-by: Miroslav Benes <mbenes@suse.cz>
M
next prev parent reply other threads:[~2019-11-29 18:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 9:55 [PATCH v3 0/4] s390/livepatch: Implement reliable stack tracing for the consistency model Miroslav Benes
2019-11-06 9:55 ` [PATCH v3 1/4] s390/unwind: drop unnecessary code around calling ftrace_graph_ret_addr() Miroslav Benes
2019-11-28 16:51 ` Vasily Gorbik
2019-11-06 9:55 ` [PATCH v3 2/4] s390/unwind: split unwind_next_frame() to several functions Miroslav Benes
2019-11-06 9:56 ` [PATCH v3 3/4] s390/unwind: prepare the unwinding interface for reliable stack traces Miroslav Benes
2019-11-06 9:56 ` [PATCH v3 4/4] s390/livepatch: Implement reliable stack tracing for the consistency model Miroslav Benes
2019-11-29 7:41 ` Vasily Gorbik
2019-11-29 7:41 ` [PATCH v4 1/2] s390/unwind: add stack pointer alignment sanity checks Vasily Gorbik
2019-11-29 18:16 ` Miroslav Benes [this message]
2019-11-29 7:41 ` [PATCH v4 2/2] s390/livepatch: Implement reliable stack tracing for the consistency model Vasily Gorbik
2019-11-29 18:16 ` Miroslav Benes
2019-11-29 18:16 ` [PATCH v3 4/4] " Miroslav Benes
2019-12-11 13:45 ` Libor Pechacek
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=alpine.LSU.2.21.1911291533310.23789@pobox.suse.cz \
--to=mbenes@suse.cz \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=nstange@suse.de \
--cc=pmladek@suse.com \
/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).