linux-kernel - Re: [GIT PULL] x86/uapi for 3.8

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: <CA+55aFy_xU6FryKX+pJ697B3+jRjRTniEVxn4quCs-tB-Qz7rw@mail.gmail.com>
Date:	Sun, 16 Dec 2012 12:12:21 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Matt Fleming <matt.fleming@...el.com>
Cc:	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	David Howells <dhowells@...hat.com>,
	Grant Likely <grant.likely@...retlab.ca>,
	Guennadi Liakhovetski <g.liakhovetski@....de>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Arnd Bergmann <arnd@...db.de>, Dave Jones <davej@...hat.com>,
	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Michael Kerrisk <mtk.manpages@...il.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [GIT PULL] x86/uapi for 3.8

On Sun, Dec 16, 2012 at 6:54 AM, Matt Fleming <matt.fleming@...el.com> wrote:
>
> At least we now know the problem wasn't caused by a memory map issue,
> just my buggy patch.
>
> Linus, Peter, how should we proceed from here? Since the commit and its
> dependants have been reverted should we punt for now and try again next
> merge window?

Hmm. Since we're several days away from the merge window closing, I
think I can apply your fixed patch and then undo the revert. But I'll
need to feel confident that it works for me too, because I absolutely
detest having kernels that I can't use for development myself (which
is why I _very_ aggressively revert stuff that I notice myself: if
it's a problem reported by some random user, I try to give developers
time to fix it if they are responding to the problem report, but if
it's a problem that means that I can't use the current -git tree
myself, I tend to revert much more aggressively).

So I'll test it and see, and hope for the best,

           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/