linux-kernel - Re: [x86-tip] strange nr

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: <alpine.DEB.2.20.1609270811110.4915@nanos>
Date:   Tue, 27 Sep 2016 08:16:25 -0400 (EDT)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Dou Liyang <douly.fnst@...fujitsu.com>
cc:     Mike Galbraith <umgwanakikbuti@...il.com>,
        Ingo Molnar <mingo@...e.hu>,
        LKML <linux-kernel@...r.kernel.org>,
        Borislav Petkov <bp@...en8.de>
Subject: Re: [x86-tip] strange nr_cpus= boot regression

On Tue, 27 Sep 2016, Dou Liyang wrote:
> In fact, it's my fault.
> I should re-base my patches after the commit c291b0151585 in time.

Definitely not your fault. As a maintainer I should have been more careful
and check whether Linus tree or x86/urgent has any modifications to that
area before applying your patches. 

> I learned a lot from it.

We all did. 

Thanks,

	tglx