linux-kernel - Re: build failure of malta_qemu_32r6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210409121637.GA13010@alpha.franken.de>
Date:   Fri, 9 Apr 2021 14:16:37 +0200
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     YunQiang Su <wzssyqa@...il.com>
Cc:     Sudip Mukherjee <sudipm.mukherjee@...il.com>,
        linux-mips <linux-mips@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: build failure of malta_qemu_32r6_defconfig

On Thu, Apr 08, 2021 at 09:42:11AM +0800, YunQiang Su wrote:
> Sudip Mukherjee <sudipm.mukherjee@...il.com> 于2021年4月8日周四 上午2:26写道：
> >
> > Hi Thomas,
> >
> > I was building v5.10.28 with malta_qemu_32r6_defconfig and noticed that
> > it fails to build, so tried next-20210407 to see if it has been fixed.
> > But linux-next also has the issue with gcc-10.
> >
> > The error is:
> >
> > ./arch/mips/include/asm/vdso/gettimeofday.h: In function '__vdso_clock_gettime':
> > ./arch/mips/include/asm/vdso/gettimeofday.h:103:2: error: the register 'lo' cannot be clobbered in 'asm' for the current target
> >   103 |  asm volatile(
> >       |  ^~~
> 
> this operation try to save lo and hi register, while they are not
> exisiting on r6.
> We are working on figure out a patch for it.

looks like there is already a patch in patchwork, which just needs
a workup:

https://patchwork.kernel.org/project/linux-mips/patch/20200801154401.4177009-1-romain.naour@gmail.com/

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]