linux-kernel - Re: [kbuild-all] [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions

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: <alpine.DEB.2.21.1908300802390.1938@nanos.tec.linutronix.de>
Date:   Fri, 30 Aug 2019 08:06:27 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Philip Li <philip.li@...el.com>
cc:     Borislav Petkov <bp@...e.de>, kbuild test robot <lkp@...el.com>,
        linux-input@...r.kernel.org,
        Thomas Hellstrom <thellstrom@...are.com>,
        x86-ml <x86@...nel.org>, linux-tip-commits@...r.kernel.org,
        pv-drivers@...are.com, Dmitry Torokhov <dmitry.torokhov@...il.com>,
        linux-kernel@...r.kernel.org,
        tip-bot2 for Thomas Hellstrom <tip-bot2@...utronix.de>,
        Doug Covelli <dcovelli@...are.com>,
        Ingo Molnar <mingo@...hat.com>,
        VMware Graphics <linux-graphics-maintainer@...are.com>,
        kbuild-all@...org, "H. Peter Anvin" <hpa@...or.com>,
        Ingo Molnar <mingo@...nel.org>
Subject: Re: [kbuild-all] [tip: x86/vmware] input/vmmouse: Update the backdoor
 call with support for new instructions

Philip,

On Fri, 30 Aug 2019, Philip Li wrote:

> > wanna test trees, I'd suggest simply testing TIP's tip/master branch
> > which gets redone on a daily basis instead of testing patches in the
> > tip-bot{,2} notification mails.
>
> Thanks Boris for the input. Besides the repo monitoring, we also check the patches
> in mailing lists, and try to apply patch to a suitable base. Do you think we can
> skip the mailing list of tip-bot{,2}?

As I just explained in a reply to another random build failure caused by this.

tip-bot2 is a notification mechanism to let people know that a particular
patch has been merged into one of the tip tree branches. These mails are
also properly threaded most of the time and reply to the patch which was
sent to the mailing list.

So yes, randomly picking patches from tip-bot2 is not useful at all. The
mails contain the information to which tip branch the patch has been
applied, so the only useful information for your bot is to select the
branch which got the new patches and start testing on that one.

Thanks,

	tglx