linux-kernel - Re: Linux 3.11-rc2

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:	Mon, 22 Jul 2013 11:11:54 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	James Hogan <james@...anarts.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kamal Mostafa <kamal@...onical.com>,
	Matthew Garrett <matthew.garrett@...ula.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	Steven Newbury <steve@...wbury.org.uk>
Subject: Re: Linux 3.11-rc2

On Mon, Jul 22, 2013 at 6:02 AM, Rafael J. Wysocki <rjw@...k.pl> wrote:
>
> Linus, do you want me to send a pull request reverting 8c5bd7a and efaa14c?

Yes, but let's wait a while. Not because I think we'll fix the problem
(hey, miracles might happen), but because I think it would be useful
to couple the reverts with information about the particular machines
that broke (and the people who reported it). So that when we
inevitably try again, we can perhaps get some testing effort with
those machines/people.

It doesn't seem to be a show-stopped for a large number of people, so
there's no huge hurry. I'd suggest doing the revert just in time for
rc3, but waiting until then to gather info about people who see
breakage.

Sound like a plan?

                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/