From: Akira Tsukamoto <akira.tsukamoto@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Palmer Dabbelt <palmer@dabbelt.com>
Cc: linux-riscv@lists.infradead.org
Subject: Re: Linux 5.14-rc2
Date: Wed, 21 Jul 2021 09:26:23 +0900 [thread overview]
Message-ID: <06a1a5fa-3d3e-8037-ee6c-74acc16a0df3@gmail.com> (raw)
In-Reply-To: <CAHk-=wivYZGxR4oumBk_rTAstRx=WWpwBAgS7n3M5ydbd0rTzQ@mail.gmail.com>
On 7/21/2021 2:24 AM, Linus Torvalds wrote:
> Don't know if you guys saw these mainline -rc reports:
>
> https://lore.kernel.org/lkml/2c03b355-86dd-1fa6-dbaf-5857f4a45a66@roeck-us.net/
> https://lore.kernel.org/lkml/20210719140437.GA2178213@roeck-us.net/
>
> On Mon, Jul 19, 2021 at 7:05 AM Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> Failed builds:
>> riscv32:allmodconfig
>> riscv:allmodconfig
>>
>> No major change here, except that arcv2 images now build.
>> For reference, the riscv build problem is:
>>
>> cc1: error: '4496' is not a valid offset in '-mstack-protector-guard-offset='
>
> and from the -rc1 one from Guenter:
>
>> The riscv:allmodconfig build failure is not new. It is seen if both
>> STACKPROTECTOR_PER_TASK and GCC_PLUGIN_RANDSTRUCT are enabled.
>> See
>> https://patchwork.kernel.org/project/linux-riscv/patch/20210706162621.940924-1-linux@roeck-us.net/
>> for details and a proposed fix.
>>
>> riscv32 images fail to boot due to commit ca6eaaa210de ("riscv:
>> __asm_copy_to-from_user: Optimize unaligned memory access and pipeline
>> stall"). I reported this a couple of days ago, but have not seen a reply.
>
> it would be nice to have these basic tests all passing again.
I have sent the fixes yesterday in my time.
https://lists.infradead.org/pipermail/linux-riscv/2021-July/007621.html
Guenter and Geert have confirmed the fix.
https://lists.infradead.org/pipermail/linux-riscv/2021-July/007634.html
https://lists.infradead.org/pipermail/linux-riscv/2021-July/007626.html
Akira
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-07-21 0:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=wjYghA5O+ZsWKVNApMK3j4V1EibO5P+c4MrHnqp8YhY=g@mail.gmail.com>
[not found] ` <20210719140437.GA2178213@roeck-us.net>
2021-07-20 17:24 ` Linux 5.14-rc2 Linus Torvalds
2021-07-20 17:27 ` Linus Torvalds
2021-07-21 0:26 ` Akira Tsukamoto [this message]
2021-07-24 0:58 ` Palmer Dabbelt
2021-07-25 9:56 ` Akira Tsukamoto
2021-08-09 16:19 ` Palmer Dabbelt
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=06a1a5fa-3d3e-8037-ee6c-74acc16a0df3@gmail.com \
--to=akira.tsukamoto@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=torvalds@linux-foundation.org \
/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