From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Derek Parker <parkerderek86@gmail.com>,
Dmitrii Okunev <xaionaro@gmail.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Possible regression by ab037dd87a2f (powerpc/vdso: Switch VDSO to generic C implementation.)
Date: Tue, 27 Jul 2021 10:45:48 +0200 [thread overview]
Message-ID: <a273c619-9258-e29a-24c3-ea47a13c4817@molgen.mpg.de> (raw)
Dear Christophe,
On ppc64le Go 1.16.2 from Ubuntu 21.04 terminates with a segmentation
fault [1], and it might be related to *[release-branch.go1.16] runtime:
fix crash during VDSO calls on PowerPC* [2], conjecturing that commit
ab037dd87a2f (powerpc/vdso: Switch VDSO to generic C implementation.)
added in Linux 5.11 causes this.
If this is indeed the case, this would be a regression in userspace. Is
there a generic fix or should the change be reverted?
Kind regards,
Paul
[1]: https://github.com/9elements/converged-security-suite/issues/268
[2]: https://go-review.googlesource.com/c/go/+/334410/
[3]:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab037dd87a2f946556850e204c06cbd7a2a19390
next reply other threads:[~2021-07-27 8:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 8:45 Paul Menzel [this message]
2021-07-27 23:14 ` Possible regression by ab037dd87a2f (powerpc/vdso: Switch VDSO to generic C implementation.) Benjamin Herrenschmidt
2021-07-28 8:26 ` Paul Menzel
2021-07-28 12:43 ` Michael Ellerman
2021-07-28 12:53 ` Paul Menzel
2021-07-29 7:41 ` Michael Ellerman
2021-07-29 8:33 ` Paul Menzel
2021-07-29 12:58 ` Michael Ellerman
[not found] ` <875ywt1s9r.fsf__45665.8238823124$1627544516$gmane$org@mpe.ellerman.id.au>
2021-07-29 8:48 ` Andreas Schwab
2021-08-02 6:04 ` Michael Ellerman
[not found] ` <OF44F7146F.67A4C1C2-ON00258720.004DBF64-00258720.004FCFCC@ibm.com>
2021-08-02 6:18 ` Michael Ellerman
2021-08-02 12:48 ` Benjamin Herrenschmidt
2021-08-02 18:07 ` Segher Boessenkool
2021-08-02 18:14 ` Lynn Boger
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=a273c619-9258-e29a-24c3-ea47a13c4817@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=parkerderek86@gmail.com \
--cc=paulus@samba.org \
--cc=xaionaro@gmail.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).