linux-kernel - Re: [kbuild-all] Re: [linux-next:master 13538/13785] /tmp/metronomefb-846872.s:300: Error: unrecognized opcode `zext.b a2,a2'

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] [day] [month] [year] [list]

Message-ID: <20201219142526.GA20452@intel.com>
Date:   Sat, 19 Dec 2020 22:25:26 +0800
From:   Philip Li <philip.li@...el.com>
To:     Pavel Machek <pavel@....cz>
Cc:     kernel test robot <lkp@...el.com>,
        kernel list <linux-kernel@...r.kernel.org>,
        Zheng Yongjun <zhengyongjun3@...wei.com>,
        kbuild-all@...ts.01.org, clang-built-linux@...glegroups.com,
        Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: [kbuild-all] Re: [linux-next:master 13538/13785]
 /tmp/metronomefb-846872.s:300: Error: unrecognized opcode `zext.b a2,a2'

On Sat, Dec 19, 2020 at 02:15:28PM +0100, Pavel Machek wrote:
> Hi!
> 
> > > > Crazy robot, stop spamming. This report is obviously bogus, yet, you
> > > > sent me 5 copies.
> > > Thanks Pavel for input, sorry for the false positive. It tries to
> > > bisect error like below (the new error), but it may be related to
> > > assember support. We will adjust the system to not report this out
> > > wrongly. Kindly allow some time for us to resolving this.
> > > 
> > > > > >> /tmp/metronomefb-846872.s:300: Error: unrecognized opcode `zext.b a2,a2'
> > > 
> > > Thanks
> > > 
> > > > 
> > > > Whoever is responsible for this, please sign emails with your real
> > > > name!
> > This is Philip who maintains the 0-day ci, and lkp@...el.com is the
> > mailing list for the team here to be contacted.
> 
> Yes, so... 0-day bot normally does a really good job (and thanks for
> it).
> 
> But getting emails from robot is slightly annoying, and it would be
> nice to include name of person who is primary responsible from the bot
> somewhere.
> 
> If you are primary person responsible for the robot, your name should
> be somewhere in the email. Or perhaps the link in the trailer should
> lead to explanation somewhere.
Thanks for advice, I will consider this and add the appropriate web link in
the end of mail after polishing the current info.

> 
> Best regards,
> 								Pavel
> -- 
> http://www.livejournal.com/~pavelmachek