linux-kernel - Re: the maxcpus= boot parameter broke somewhere along the line

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]

Date:	Wed, 07 Mar 2012 21:11:12 +0530
From:	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
To:	Jeff Moyer <jmoyer@...hat.com>
CC:	Sasha Levin <levinsasha928@...il.com>,
	Nick Bowler <nbowler@...iptictech.com>,
	linux-kernel@...r.kernel.org
Subject: Re: the maxcpus= boot parameter broke somewhere along the line

On 03/06/2012 11:38 PM, Jeff Moyer wrote:

> Sasha Levin <levinsasha928@...il.com> writes:
> 
>> I can't reproduce it locally with a 3.3-rc5 kernel.
> 
> First, thanks for looking into it.  I just did a git pull, up to -rc6,
> and the problem still persists on my machine.
>


I tried 3.3-rc4 as well as 3.3-rc6+ (last commit dac12d1). I did not
see the problem in either case.


> Again, let me know if there's anything else I can provide that would be
> helpful for debugging this.
> 


Regards,
Srivatsa S. Bhat
IBM Linux Technology Center

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/