linux-kernel - Re: [Bug #13116] Can't boot with nosmp

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: <20090609135846.43260595@nehalam>
Date:	Tue, 9 Jun 2009 13:58:46 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Avi Kivity <avi@...hat.com>
Cc:	Dan Williams <dan.j.williams@...el.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: [Bug #13116] Can't boot with nosmp

On Tue, 09 Jun 2009 21:42:55 +0300
Avi Kivity <avi@...hat.com> wrote:

> Stephen Hemminger wrote:
> 
>   
> 
> >> This only affects reboots.  But yes, the cpumask code has bugs.  Does 
> >> the .config involved select MAXSMP?
> >>
> >>     
> >
> > Patch does not fix the problem. Not sure if it is KVM only problem.
> > Look like possible cpumask always equals what ACPI / SMP tables report.
> > So currently looking into alloc_percpu which may not handle the possible
> > but never used cpus.
> >
> >   
> 
> Right, it shouldn't have.
> 
> > It is x86-64 config and does not have MAXSMP set. It does have NR_CPUS set.
> >   
> 
> So it's not cpumask.  Dare I suggest a bisect?
> 

I did some testing of different versions.

* Problem does not exist with 2.6.30-rc8 (so regression should be closed).

* Problem does exist with 2.6.29.4

* Happens with both nosmp and maxcpus=1


Given that it is fixed in 2.6.30, at this point there really is no urgency
to spend more time investigating the issue. There are certainly bigger problems
to deal with.

-- 
--
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/