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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sat, 7 Jan 2012 11:29:09 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Ben Hutchings <ben@...adent.org.uk>
Cc:	Greg KH <gregkh@...e.de>,
	Geert Uytterhoeven <geert@...ux-m68k.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 6, 2012 at 2:31 PM, Ben Hutchings <ben@...adent.org.uk> wrote:
>
> 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.

Ok, let's try to move forward, and just have those architectures add
the appropriate "register_cpu()" calls. I can live with them breaking
for a short while, and hopefully me merging this will result in it
quickly being fixed.

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