linux-kernel - Re: [PATCH v4 0/16] Merge ram_console into pstore, and more

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: <CAGXu5jKAa78FC07TAHKp1tVh+qUt_9TmZk437nupNUVxs2BqtA@mail.gmail.com>
Date:	Tue, 22 May 2012 12:09:47 -0700
From:	Kees Cook <keescook@...omium.org>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	devel@...verdev.osuosl.org, Tony Luck <tony.luck@...el.com>,
	Arnd Bergmann <arnd@...db.de>, patches@...aro.org,
	Marco Stornelli <marco.stornelli@...il.com>,
	Stephen Boyd <sboyd@...eaurora.org>,
	linux-kernel@...r.kernel.org,
	Anton Vorontsov <anton.vorontsov@...aro.org>, arve@...roid.com,
	linaro-kernel@...ts.linaro.org,
	John Stultz <john.stultz@...aro.org>,
	Shuah Khan <shuahkhan@...il.com>,
	Jesper Juhl <jj@...osbits.net>,
	Colin Cross <ccross@...roid.com>,
	Rebecca Schultz Zavin <rebecca@...roid.com>,
	WANG Cong <xiyou.wangcong@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	kernel-team@...roid.com, Thomas Meyer <thomas@...3r.de>
Subject: Re: [PATCH v4 0/16] Merge ram_console into pstore, and more

On Tue, May 22, 2012 at 12:04 PM, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> On Tue, May 22, 2012 at 11:33:33AM -0700, Kees Cook wrote:
>> On Tue, May 22, 2012 at 11:19 AM, Greg Kroah-Hartman
>> <gregkh@...uxfoundation.org> wrote:
>> > On Tue, May 22, 2012 at 07:17:17AM -0700, Anton Vorontsov wrote:
>> >> Hi all,
>> >>
>> >> A brand new v4:
>> >>
>> >> - Per Kees Cook's comments, the patches no longer remove an automatic
>> >>   updates feature, but instead make the it configurable; plus disable
>> >>   it by default (in a separate patch);
>> >> - Fixed some bugs noticed by Colin Cross;
>> >> - Documented new continuous ramoops-console log behaviour (also
>> >>   noticed by Colin Cross).
>> >
>> > In case you were wondering, all of this is going to have to wait for
>> > 3.6, as the 3.5 merge window with my trees have been closed.  I'll be
>> > able to start accepting patches once 3.5-rc1 is out, so take your time
>> > in getting this all working properly, there's no rush here.
>>
>> Will the ramoops stuff that was in -next (via -mm) that now landed in
>> -staging make it sanely into 3.5? Specifically the two patches at the
>> top of:
>> http://git.kernel.org/?p=linux/kernel/git/kees/linux.git;a=shortlog;h=refs/heads/ramoops
>
> Anything that was in staging and linux-next already, yes, will go in for
> 3.5, I've already sent Linus the pull request for that.
>
> Is that a problem?

No problem at all -- it missed 3.4 on a technicality, and I didn't
want it to miss 3.5 too. :)

Thanks!

-Kees

-- 
Kees Cook
Chrome OS Security
--
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/