From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Greentime Hu <greentime.hu@sifive.com>,
Vincent Chen <vincent.chen@sifive.com>,
Vineet Gupta <vineetg@rivosinc.com>,
Richard Henderson <richard.henderson@linaro.org>,
Andy Chiu <andy.chiu@sifive.com>,
Conor Dooley <conor.dooley@microchip.com>,
Heiko Stuebner <heiko.stuebner@vrull.eu>,
Palmer Dabbelt <palmer@rivosinc.com>,
matoro <matoro_bugzilla_kernel@matoro.tk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux RISC-V <linux-riscv@lists.infradead.org>
Subject: Fwd: [bisected][regression] rustc userspace crashes on riscv in kernel 6.5
Date: Fri, 22 Sep 2023 07:02:09 +0700 [thread overview]
Message-ID: <49a92f24-bd70-483c-aaaa-49d00c339b12@gmail.com> (raw)
Hi,
I notice a regression report on Bugzilla [1]. Quoting from it:
> Since this commit:
>
> commit 8ee0b41898fa26f66e32237f179b6989c65600d6
> Author: Greentime Hu <greentime.hu@sifive.com>
> Date: Mon Jun 5 11:07:11 2023 +0000
>
> riscv: signal: Add sigcontext save/restore for vector
>
> running rustc on riscv produces output like this:
>
> $ rustc test.rs
> /usr/lib/rust/lib/librustc_driver-f0248bec779deb29.so(+0xe8ebdc)[0x3f8dc8ebdc]
> linux-vdso.so.1(__vdso_rt_sigreturn+0x0)[0x3f8fb91800]
> /lib64/libc.so.6(syscall+0x16)[0x3f8cbfacbe]
> /usr/lib/rust/lib/libstd-985e4b663b8154c3.so(_ZN3std3sys4unix5locks13futex_condvar7Condvar4wait17h4e3b669d2690824dE+0x64)[0x3f8cd45f68]
> /usr/lib/rust/lib/librustc_driver-f0248bec779deb29.so(+0x715ab6)[0x3f8d515ab6]
> /usr/lib/rust/lib/librustc_driver-f0248bec779deb29.so(+0x7159ce)[0x3f8d5159ce]
> /usr/lib/rust/lib/librustc_driver-f0248bec779deb29.so(+0x6b64f6)[0x3f8d4b64f6]
> /usr/lib/rust/lib/librustc_driver-f0248bec779deb29.so(+0x715534)[0x3f8d515534]
> /usr/lib/rust/lib/libstd-985e4b663b8154c3.so(rust_metadata_std_9e9c65f710e3ce43+0xaba32)[0x3f8cd44a32]
> /lib64/libc.so.6(+0x6a8e4)[0x3f8cbab8e4]
> /lib64/libc.so.6(+0xbb49c)[0x3f8cbfc49c]
>
> even for a simple hello world program. The output being present does not necessarily mean that the compilation failed, in fact often it will still return 0 and produce a working binary despite the output, but often it does not, frequently enough that it's impossible to build large rust packages. See the attached log for an example of a real build which fails partway through (despite the fact that all compilation lines emit the traceback).
See Bugzilla for the full thread and attached rust build log.
The reporter (Cc'ed) confirms that this regression occurs on all rust toolchain
distributions (both from the distro and from rustup (maybe?)).
Anyway, I'm adding it to regzbot:
#regzbot introduced: 8ee0b41898fa26 https://bugzilla.kernel.org/show_bug.cgi?id=217923
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217923
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-09-22 0:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 0:02 Bagas Sanjaya [this message]
2023-10-16 8:22 ` Linux regression tracking #update (Thorsten Leemhuis)
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=49a92f24-bd70-483c-aaaa-49d00c339b12@gmail.com \
--to=bagasdotme@gmail.com \
--cc=andy.chiu@sifive.com \
--cc=conor.dooley@microchip.com \
--cc=greentime.hu@sifive.com \
--cc=heiko.stuebner@vrull.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=matoro_bugzilla_kernel@matoro.tk \
--cc=palmer@rivosinc.com \
--cc=regressions@lists.linux.dev \
--cc=richard.henderson@linaro.org \
--cc=vincent.chen@sifive.com \
--cc=vineetg@rivosinc.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
all inboxes | Powered by JetHome®