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: <20190830080650.GA30413@zn.tnic>
Date:   Fri, 30 Aug 2019 10:06:50 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Philip Li <philip.li@...el.com>
Cc:     Thomas Gleixner <tglx@...utronix.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

On Fri, Aug 30, 2019 at 02:20:53PM +0800, Philip Li wrote:
> thanks for your patience. I just realize we actually block tip-bot, but
> not tip-bot2. I will update the logic to avoid this issue, and we will
> keep monitor for a while to fix new issue if any.

... and just to reiterate: it would be a *lot-lot* more useful if you
guys tested the single tip branches or the combined tip/master on a
daily basis as that is the x86 queue that goes to Linus eventually. That
is, if you do not test it already. But we don't get any "we tested this
branch" email so I'm thinking you don't...

Thx.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.