linux-kernel - Re: Stable -rc git trees and email headers

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: <m2r3brag0j.fsf@baylibre.com>
Date:	Mon, 20 Jun 2016 11:09:48 -0700
From:	Kevin Hilman <khilman@...libre.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Guenter Roeck <linux@...ck-us.net>,
	Fengguang Wu <fengguang.wu@...el.com>, stable@...r.kernel.org,
	linux-kernel@...r.kernel.org, milo.casagrande@...aro.org,
	tyler.baker@...aro.org
Subject: Re: Stable -rc git trees and email headers

Greg KH <gregkh@...uxfoundation.org> writes:

> Hi,
>
> I've finally gotten off my butt and made my quilt trees of patches into
> a "semi-proper" git tree to make it easier for people to test them.
>
> I'm now pushing the patches I accept into the stable queues into the git
> tree here:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>
> I'll push them out in chunks, as I accept them, and when I do a "real"
> -rc release.  Right now the HEAD of each branch will have a -rc1 tag on
> them, just because it makes it a bit easier on my end.
>
> Note these branches WILL get rebased.  All the time.  So don't count on
> them to contain anything that will stick around, UNTIL a real stable
> release happens.
>
> Guenter, I hope this helps with your testing, is there anything that I
> can do here to make it easier for you?
>
> Kevin, hopefully this tree also helps you.  I will also be adding some
> email headers to my announcements of the -rc releases that you can
> parse.  Here is what they are going to look like for an example release:
>
> X-KernelTest-Patch: http://kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.14-rc1.gz
> X-KernelTest-Tree: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> X-KernelTest-Branch: linux-4.4.y
> X-KernelTest-Patches: git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
> X-KernelTest-Version: 4.4.14-rc1
> X-KernelTest-Deadline: 2016-06-20T02:57+00:00
>
> Will those work out?

Yes, those look great.  We'll start swtiching the kernelci.org bot over
to this tree and let you know if there's anything else we need.

> Fengguang, can you add these to the 0-day bot?  The branches to watch
> are all of the currently-active stable trees.  Right now that would be
> "linux-3.14.y", "linux-4.4.y", and "linux-4.6.y".  Do I need to tell you
> about future branches, or can you just pick up new ones when they show
> up?
>
> And can I get announcements if/when the tests pass (or fail) so I know
> all is ok?
>
> Hope this helps people out,

Yes, it does.  Thanks!

Kevin