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: <73a9013d-92d2-04fd-3621-360ef48f6554@alibaba-inc.com>
Date:   Wed, 03 Jan 2018 20:24:59 +0800
From:   "Jia Zhang" <qianyue.zj@...baba-inc.com>
To:     Borislav Petkov <bp@...en8.de>, kbuild test robot <lkp@...el.com>
Cc:     kbuild-all@...org, mingo@...hat.com, hpa@...or.com,
        tglx@...utronix.de, tony.luck@...el.com, x86@...nel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5] x86/microcode/intel: Blacklist the specific BDW-EP for
 late loading



在 2018/1/3 上午4:57, Borislav Petkov 写道:
> On Wed, Jan 03, 2018 at 04:49:42AM +0800, kbuild test robot wrote:
>> Hi Jia,
>>
>> Thank you for the patch! Yet something to improve:
>>
>> [auto build test ERROR on v4.15-rc5]
>> [also build test ERROR on next-20180102]
>> [cannot apply to tip/x86/core]
>> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>>
>> url:    https://github.com/0day-ci/linux/commits/Jia-Zhang/x86-microcode-intel-Blacklist-the-specific-BDW-EP-for-late-loading/20180103-040752
>> config: i386-randconfig-x010-201800 (attached as .config)
>> compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
>> reproduce:
>>         # save the attached .config to linux build tree
>>         make ARCH=i386 
>>
>> All errors (new ones prefixed by >>):
>>
>>    arch/x86/kernel/cpu/microcode/intel.c: In function 'is_blacklisted':
>>>> arch/x86/kernel/cpu/microcode/intel.c:920:7: error: 'struct cpuinfo_x86' has no member named 'x86_stepping'
>>          c->x86_stepping == 0x01 && c->microcode < 0x0b000021) {
>>           ^~
> 
> Yeah, already fixed that:
> 
> https://lkml.kernel.org/r/20180101221056.eav4buwnpqhudei6@pd.tnic

So what is the best moment to resend a V3 patch for "x86: clean up
confusing x86_mask" to correct x86_mask for this?

Thanks,
Jia

> 
> Thx!
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ