linux-kernel - Re: [GIT PATCH] driver core merge for 3.3

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 6 Jan 2012 22:31:48 +0000
From:	Ben Hutchings <ben@...adent.org.uk>
To:	Greg KH <gregkh@...e.de>
Cc:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Linux-Arch <linux-arch@...r.kernel.org>
Subject: Re: [GIT PATCH] driver core merge for 3.3

On Fri, Jan 06, 2012 at 02:06:08PM -0800, Greg KH wrote:
> On Fri, Jan 06, 2012 at 10:38:41PM +0100, Geert Uytterhoeven wrote:
> > On Fri, Jan 6, 2012 at 21:11, Greg KH <gregkh@...e.de> wrote:
> > > Ben Hutchings (1):
> > >      topology: Provide CPU topology in sysfs in !SMP configurations
> > 
> > FWIW, as reported before, I can confirm that 3.2.0-next-20120106 crashes
> > on m68k during boot:
[...]
> > Disabling lock debugging due to kernel taint
> > Kernel panic - not syncing: Attempted to kill init!
> > 
> > Reverting the above commit (ccbc60d3e19a1b6ae66ca0d89b3da02dde62088b)
> > fixes it.
> > 
> > So to preserve bisectability, you may want to drop this ommit until the
> > UP-only archs have been fixed.
> 
> Ick, sorry for missing that report, you are right.
> 
> Ben, I thought this patch was for UP systems, how did this work on your
> testing?

It works just fine on UP x86.  However I have been made aware that
it breaks on m68k and I told you as much in
<1325462025.13595.189.camel@...deye>:

> None of these architectures appears to call register_cpu():
> 
>     c6x frv h8300 m68k microblaze openrisc score um xtensa
> 
> and therefore they will all panic at boot following this change (commit
> ccbc60d3e19a1b6ae66ca0d89b3da02dde62088b).  So either I can try to fix
> them or else it must be reverted for now.

Ben.

> Linus, can you revert this, or I can if you want me to.
> 
> thanks,
> 
> greg k-h
> 

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                              - Albert Camus
--
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/