On Wed, Mar 29, 2023 at 06:41:41AM +0000, Conor.Dooley@xxxxxxxxxxxxx wrote:
On 29/03/2023 01:33, Nathan Chancellor wrote:
EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
On Tue, Mar 28, 2023 at 08:40:02AM -0700, Nathan Chancellor wrote:
On Tue, Mar 28, 2023 at 12:57:24PM +0000, Conor.Dooley@xxxxxxxxxxxxx wrote:
On 28/03/2023 13:47, gregkh@xxxxxxxxxxxxxxxxxxx wrote:
EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
This is a note to let you know that I've just added the patch titled
riscv: Handle zicsr/zifencei issues between clang and binutils
I think this needs a custom backport to kernels prior to 5.15 as the
as_version checking didn't yet exist.
I think this needs to be dropped from the 5.10 and 5.4 stable trees as
a result.
Indeed, this report I just received shows this patch does nothing on its
own on 5.10 and earlier:
https://lore.kernel.org/202303282359.tiuafpnd-lkp@xxxxxxxxx/
I am not sure it is worth the backport complexity to try and fix this in
5.4, as there is very little testing or real world usage for RISC-V and
clang at that point, but I will see how 5.10 goes and decide from there.
I submitted the 5.10 backports here:
https://lore.kernel.org/20230328-riscv-zifencei-zicsr-5-10-v1-0-bccb3e16dc46@xxxxxxxxxx/
I do not think this is worth fixing in 5.4, as it is missing other
RISC-V fixes with clang.
I doubt many people people care about 5.4, let alone 5.4 with a mix of
bleeding edge(ish in the case of gcc) toolchains, outside of CI.
I think you're safe to ignore it there, as even the CIs didn't hit it
on 5.4.
We can revisit things iff someone is emotionally invested in such a
combo...
Okay, I've dropped it from both 5.4 and 5.10, we can revisit the
backport after the upcoming release.
--
Thanks,
Sasha
